Menu
Structured code review focusing on correctness, security, and maintainability. Correctness before style. Every reviewer comment must be actionable.
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
Automated quality gates from commit to production. Every merge to main is potentially shippable. No manual steps in the deployment path.
Document decisions, not just implementations. ADRs for architectural choices, inline docs for non-obvious code, and runbooks for operational knowledge.
Graceful degradation and meaningful error messages. Errors are first-class citizens, not afterthoughts. Every error path is designed, not discovered.
Test real system boundaries, not mocks of mocks. Integration tests verify that components work together, not that they work in isolation.
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
Safe, behavior-preserving code transformation backed by tests. Refactor with evidence, not instinct.
| name | code-review |
| description | Structured code review focusing on correctness, security, and maintainability. Correctness before style. Every reviewer comment must be actionable. |
| category | review |
| applies-to | ["claude","gemini","cursor","copilot","any"] |
| version | 1.0.0 |
Code review is the last line of defense before code reaches production. This skill structures the review process to catch real issues — not just style preferences — and ensures every comment is actionable and proportionate.
Verify: You understand what the PR is trying to accomplish.
Verify: You can trace the execution path for the primary use case and 2 failure cases.
{username} — use parameterized queries."| Excuse | Rebuttal |
|---|---|
| "I'll review it quickly" | A rushed review is not a review. Take the time or ask someone who can. |
| "The tests pass so it's fine" | Tests prove the code works for tested inputs, not that it's secure or maintainable. |
| "I'll comment on style later" | Style comments without blocker separation waste everyone's time. Label them. |