菜单
Use when the user wants to generate a pull/merge request (PR/MR) summary for the changes in the current branch
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/epam/ai-dial-admin-evaluation-framework-backend --skill pr-summary命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| 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.
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.
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.
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".