Menu
Generate PR summary by comparing code differences with parent branch. Uses PR template and outputs to ./report/PR_SUMMARY.MD.
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.
Based on SOC occupation classification
Security and quality review of code changes. Supports branch comparison (default) and uncommitted changes modes.
Full codebase consistency scan. Checks all hand-written source files against project coding rules for style, pattern, and quality violations. Excludes auto-generated files and node_modules. Use periodically (e.g. before a release or after onboarding new team members) to catch drift from project standards.
Pre-PR quality check with adaptive agent selection, code simplification with user approval, and optimized validation. Scales review depth by diff size.
Post-implementation side effect analysis. Checks consumer impact, shared state, UI components, function signatures, and layout cascade for unintended regressions.
Show concise summary of all changes on current branch vs parent branch. Outputs grouped bullet-point list.
Create React UI components. Use when building new components, forms, dialogs, data tables, or implementing UI features. Guides through component creation workflow from planning to verification.
| name | pr-summary |
| description | Generate PR summary by comparing code differences with parent branch. Uses PR template and outputs to ./report/PR_SUMMARY.MD. |
| disable-model-invocation | true |
.github/PULL_REQUEST_TEMPLATE.md file for the template.report/PR_SUMMARY.MD (create the report/ directory if it doesn't exist).The parent branch is NOT always master. Detect it in order:
git config branch.<current>.merge to check tracking configgit log --oneline --decorate --first-parent to find the branch pointgit merge-base with common base branches (master, main, develop) and pick the closest ancestororigin/<parent> Over LocalThe local parent branch may be stale. Always prefer origin/master over master, etc.
Check with git rev-parse --verify origin/<parent>.
Always diff against the parent branch's current remote tip, not the merge-base:
git diff origin/<parent> — shows only changes unique to this branch, even if the parent was merged ingit diff $(git merge-base <parent> HEAD) — this includes parent's own changes when the parent was merged into the branchgit status --short to identify uncommitted files