From cipherpowers
Conducts systematic code reviews of recent git commits against project standards, generating structured feedback with blocking/non-blocking issues and checklists.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cipherpowers:conducting-code-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematic code review process ensuring correctness, security, and maintainability through practice adherence and structured feedback. Tests and checks are assumed to pass - reviewer focuses on code quality.
Systematic code review process ensuring correctness, security, and maintainability through practice adherence and structured feedback. Tests and checks are assumed to pass - reviewer focuses on code quality.
Before starting:
${CLAUDE_PLUGIN_ROOT}skills/requesting-code-review/SKILL.md${CLAUDE_PLUGIN_ROOT}standards/code-review.mdCore workflow:
Note: Tests and checks are assumed to pass. Focus on code quality review.
Read these before conducting review:
${CLAUDE_PLUGIN_ROOT}skills/requesting-code-review/SKILL.md - Understand requester expectations${CLAUDE_PLUGIN_ROOT}standards/code-review.md - Standards, severity levels, project commandsDetermine scope:
git log -1 --statgit log origin/main..HEADgit diff origin/main...HEADRead standards from practices:
# Standards live in practices, not in this skill
${CLAUDE_PLUGIN_ROOT}standards/code-review.md
Review ALL severity levels:
Empty sections are GOOD if you actually checked. Missing sections mean you didn't check.
Template location:
${CLAUDE_PLUGIN_ROOT}templates/code-review-template.md
1. Check Status section exists
Does your review have ## Status: [BLOCKED | APPROVED WITH SUGGESTIONS | APPROVED]?
2. Check BLOCKING section exists
Does your review have ## BLOCKING (Must Fix Before Merge)?
3. Check NON-BLOCKING section exists
Does your review have ## NON-BLOCKING (May Be Deferred)?
4. Check Checklist section exists
Does your review have ## Checklist with all 6 categories?
5. Check for prohibited custom sections
Have you added ANY sections not listed above (examples of PROHIBITED sections: Strengths, Code Quality Metrics, Assessment, Recommendations, Requirements Verification, Comparison to Previous Reviews, Reviewer Notes, Sign-Off, Review Summary, Issues with subsections, Test Results, Check Results, Next Steps)?
6. Save review file
All required sections present, no custom sections → Save to work directory.
File naming: See ${CLAUDE_PLUGIN_ROOT}standards/code-review.md for .work directory location and naming convention ({YYYY-MM-DD}-review-{N}.md).
Additional context allowed: You may add supplementary details AFTER the Checklist section (verification commands run, files changed, commit hashes). But the 4 required sections above are mandatory and must appear first in the exact order shown.
NEVER skip:
Common rationalizations that violate workflow:
Note: Tests and checks are assumed to pass. Reviewers focus on code quality, not test execution.
Requestion code review:
${CLAUDE_PLUGIN_ROOT}skills/requesting-code-review/SKILL.mdWhen receiving feedback on your review:
${CLAUDE_PLUGIN_ROOT}skills/receiving-code-review/SKILL.mdSee test-scenarios.md for pressure tests validating this workflow resists rationalization.
npx claudepluginhub cipherstash/cipherpowers --plugin cipherpowersPerforms systematic code review using standardized checklists across 8 categories (functionality, design, quality, readability, tests, security, performance, error handling) with BLOCKING/IMPORTANT/SUGGESTION/QUESTION/NOTE prefixes.
Performs code reviews using Codex MCP with severity-grouped findings and a merge gate. Supports fast (diff-only), full (diff + lint/build), and branch review variants.
Provides structured code review processes, conventional comments patterns, language-specific checklists, and feedback templates for PR reviews and standardizing practices.