Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.
View on GitHubSelect agents to install to:
npx add-skill https://github.com/TheBushidoCollective/han/blob/main/core/skills/code-reviewer/SKILL.md -a claude-code --skill code-reviewerInstallation paths:
.claude/skills/code-reviewer/# Code Reviewer Provides a systematic approach to conducting code reviews. Focuses on the **review process** and **quality dimensions**, not technology-specific patterns. ## Scope Use this skill to: - **Conduct systematic code reviews** using a structured process - **Evaluate code across multiple dimensions** (correctness, safety, maintainability) - **Provide constructive feedback** with clear, actionable recommendations - **Determine approval readiness** based on quality standards ### NOT for - Technology-specific patterns (see appropriate Jutsu plugins) - Detailed implementation guidance (see discipline-specific agents) ## Review Process Overview ### Phase 1: Pre-Review Preparation ### Before starting review, gather context 1. **Understand the change**: ```bash # Review the diff git diff <base-branch>...HEAD # Check scope of changes git diff --stat <base-branch>...HEAD ``` 2. **Identify relevant context**: ```bash # Find similar patterns in codebase grep -r "similar_pattern" . ``` 3. **Verify business context**: - Is there a related issue/ticket? Review requirements - What domain is impacted? - What's the user-facing impact? ### Phase 2: Systematic Review ### Review across these dimensions #### 1. Correctness - **Does it solve the stated problem?** - **Does business logic align with domain rules?** - **Are edge cases handled appropriately?** - **Do tests verify the expected behavior?** ### Check correctness by - Reading tests first to understand intended behavior - Tracing code paths through the change - Verifying error scenarios are covered - Cross-referencing with requirements #### 2. Safety - **Does it follow authorization/authentication patterns?** - **Are there breaking changes to APIs or contracts?** - **Could this expose sensitive data?** - **Are data operations safe?** - **Are there potential race conditions or data integrity issues?** ### Check safety by - Verifying access control on operatio