code-reviewerSafety 92Repository ShareFavorite skill

Workflow

2. Preparation

   • Remote: gh pr checkout <PR_NUMBER>, run preflight, read PR description and comments
   • Local: git status, git diff (working tree), git diff --staged (staged)

3. In-depth analysis across these pillars:

   • Correctness: does the code achieve its purpose without bugs?
   • Maintainability: is the code clean, well-structured, easy to modify?
   • Readability: consistent formatting, appropriate comments?
   • Efficiency: any performance bottlenecks?
   • Security: any vulnerabilities or insecure patterns?
   • Edge cases: proper error handling?
   • Testability: adequate test coverage? Suggest additional test cases.

4. Provide feedback (see output format below)

5. Cleanup (remote only): offer to switch back to default branch

<output_format>

• Summary: high-level overview
• Findings:
  • Critical: bugs, security issues, breaking changes
  • Improvements: better code quality or performance
  • Nitpicks: formatting or minor style issues (optional)
• Conclusion: Approved / Request Changes

Tone: constructive, professional, explain why changes are requested. </output_format>