Agent skill
post-pr-review
Self-review and fix PR issues after creating a PR. Use after PR creation, when user says "PRレビュー", "セルフレビュー", "PR修正", or "review my PR". Runs pr-review-toolkit and fixes critical/important issues and suggestions.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/post-pr-review
SKILL.md
Post-PR Review
Workflow
After PR creation, execute this workflow:
1. Run PR Review
Execute /pr-review-toolkit:review-pr to analyze the PR.
2. Fix Issues by Priority
Fix in this order:
- Critical Issues - Must fix immediately (security, bugs, breaking changes)
- Important Issues - Should fix (code quality, performance)
- Suggestions - Nice to have (style, minor improvements)
3. Commit and Push Fixes
After fixing each category, commit with a descriptive message that reflects the actual changes:
git add -A && git commit -m "fix: <describe what was fixed>"
git push
Use appropriate commit message based on fix type:
fix: resolve null safety issue in XxxAnalyzerfix: add missing error handling for API callsrefactor: simplify validation logic per review feedback
4. Re-run Review (Optional)
If significant changes were made, re-run /pr-review-toolkit:review-pr to verify.
Issue Categories
| Category | Action | Examples |
|---|---|---|
| Critical | Must fix | Security vulnerabilities, data loss risks, breaking changes |
| Important | Should fix | Missing error handling, performance issues, code smells |
| Suggestions | Consider | Naming improvements, documentation, minor refactors |
Notes
- Always run code-quality checks after fixes:
composer format:fix && composer analyze && composer test - If CI fails after push, check GitHub Actions status with
gh pr checks
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?