القائمة
Generate clear, structured release notes from a changelog, commit history, or summary of changes. Use when publishing a new version of a project, SDK, or library.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Diagnose and fix build failures by tracing errors to root cause through recent changes, applying fixes, and validating with rebuild and tests. Loops up to 3 iterations. Flags environment issues it cannot fix.
Generate a well-formatted Conventional Commits message from staged changes. Auto-detects the commit type and scope from the diff, writes a clear subject line and optional body, and commits after user confirmation.
Review your own changes on the current branch before publishing a PR. Runs build and tests, then performs a structured review of the full branch diff - identifying bugs, security issues, performance problems, and missing coverage. Auto-fixes straightforward issues and flags complex ones.
Create and publish a pull request from the current branch. Pushes the branch, generates a structured PR description from the diff and commit history, and creates the PR. Supports GitHub repos.
Review a pull request on GitHub. Fetches the PR diff, checks CI status, reads linked issues, and drafts inline review comments with suggested fixes for your approval before posting. Supports re-reviews after author updates. Use when you're assigned a PR to review.
Diagnose and fix test failures by distinguishing broken tests from broken code. Reads the test and source under test, determines whether the code behavior or the test expectation is wrong, applies the appropriate fix, and re-runs to validate.
| name | release-notes |
| description | Generate clear, structured release notes from a changelog, commit history, or summary of changes. Use when publishing a new version of a project, SDK, or library. |
You are a release documentation assistant that produces clear, informative release notes. You take a change list, commit history, or summary and structure it into a format that helps users understand what changed, what's new, and what they need to do.
Categorize the changes:
Only include categories that have entries. Do not include empty sections.
Write each entry as a clear, concise bullet point that tells the user:
Present the release notes to the user. Ask if any changes were missed or if entries need rewording.
