pr-summary

Use when the user wants to generate a pull/merge request (PR/MR) summary for the changes in the current branch

Repository: epam/ai-dial-admin-evaluation-framework-backend
Last source activity: July 30, 2026 at 08:37
Detected SKILL.md language: English
Stars: 3
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/epam/ai-dial-admin-evaluation-framework-backend --skill pr-summary

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

name	pr-summary
description	Use when the user wants to generate a pull/merge request (PR/MR) summary for the changes in the current branch
allowed-tools	Read Grep Glob LSP Bash(git diff:) Bash(git log:) Bash(git show:) Bash(git rev-parse:) Bash(git merge-base:) Bash(git rev-list:) Bash(mkdir -p ./tmp/pr-summary) Write(./tmp/pr-summary/*)
model	opus
effort	high
context	fork
agent	general-purpose

Provide an extreemely succint summary of the changes in the branch: two paragraphs - problem statement, solution. put md file into tmp directory. file name should be -PR-summary.

Back to search Back to installation

fe-api-handoff

Use when the user wants to hand off the current branch's changes to a frontend developer/agent — "summarize changes for the FE", "write FE handoff", "what API changes does the frontend need". Works for a raw POC branch or one or more implemented opsx changes. Diffs the current branch against `development`, and writes a single raw-HTML instruction file (wrapped in one `<important>` block, no styling) to `/tmp/fe-api-handoff/` containing the overall context plus every API contract change (endpoints, request/response DTOs, status codes & errors, enums/constants) the frontend must support. Never makes UI/UX judgments. Chat gets brief highlights + the file path only.

2026-08-21

eval-release-notes

Use when the user asks to enhance, refine, polish, or "look at" the release notes for a tag — typically a fresh CI-generated pre-release (e.g. `0.8.0-rc.1`) or a stable cut. Reads the auto-generated notes off the GitHub release, classifies and rewrites each bullet in this project's editorial voice, builds the `Deployment Changes` section from `README.md` / `docs/configuration.md` / PR bodies, and saves a draft to `claude/release-notes/`. When the target is a stable cut (e.g. `0.8.0`) and its `-rc.*` pre-releases already carry enhanced notes, it assembles the stable draft by merging those rc notes — reusing their approved wording — instead of re-deriving every bullet from the raw stable notes. Never edits GitHub directly.

2026-06-24

openspec-review-change

Review an OpenSpec change bundle for quality, consistency, and implementation readiness. Use when the user wants to analyze specs before implementation, find issues across artifacts, or assess readiness for the apply step. Similar to speckit.analyze but with iterative find-and-fix capability. Trigger for phrases like "review the spec", "check the change", "is this ready to implement", "analyze artifacts", "review before implementing".

2026-06-16

View all from this repository

pr-summary

Source facts

Install options

Review the source files

More from this repository

More from this repository