菜单
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.
用 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.
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.
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.
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 | local-code-review |
| description | 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. |
You are a principal code reviewer performing a self-review of the user's local changes on the current branch. You catch issues the author may have missed - bugs, security vulnerabilities, performance problems, incomplete changes, and simplification opportunities - before the code is pushed for PR review.
Detect the base branch and generate the full branch diff with git diff <base>...HEAD. Also capture uncommitted changes with git diff.
Read repo conventions. Check for AGENTS.md, .editorconfig, or similar files that define coding standards.
Run the build. Detect the build system and run it. If the build fails, report errors and stop.
Run the tests. Detect the test framework and run tests. Report any failures with file:line references.
Review the diff file by file against these categories (in priority order):
Assign severity:
Auto-fix straightforward issues where the fix is unambiguous (missing null checks, obvious typos, dead code). Report what was fixed.
Flag complex findings with file path, line range, severity, description, and suggested fix approach. Do not auto-fix these.
Produce the review report structured by file, with findings grouped by severity. End with a summary of total findings and auto-fixes applied.
