reviewing-code
Use when reviewing code changes, checking PRs, or evaluating code quality.
When & Why to Use This Skill
This Claude skill automates and streamlines the code review process by analyzing pull requests, evaluating code quality, and ensuring adherence to project-specific standards. It provides a structured feedback framework—ranging from critical fixes to optional improvements—helping development teams maintain high-quality codebases while catching security risks and technical debt early.
Use Cases
- Automated Pull Request Analysis: Evaluate git diffs against main branches to provide structured feedback on code changes, including a final verdict for approval or requested changes.
- Security and Secret Scanning: Automatically detect hardcoded secrets, API keys, passwords, and forgotten debug statements like 'print' or 'pdb' before code is merged.
- Code Quality Enforcement: Verify that new functionality includes necessary tests, type hints, and docstrings while ensuring the code follows established architectural patterns.
- Technical Debt Identification: Scan for 'TODO' or 'FIXME' tags within new changes to track and manage pending tasks or known issues in the codebase.
- CI/CD Pre-flight Checks: Run comprehensive validation and linting commands locally to ensure project structure integrity before pushing changes to remote repositories.
| name | reviewing-code |
|---|---|
| description | Use when reviewing code changes, checking PRs, or evaluating code quality. |
Code Review
Quick Commands
# Run ALL checks at once (tests + linting)
bpsai-pair ci
# Validate project structure
bpsai-pair validate
# See what changed
git diff main...HEAD --stat
git diff main...HEAD
Review Output Format
## Code Review: [Description]
### Summary
Brief assessment.
### Must Fix
1. **[File:Line]** - Issue and fix
### Should Fix
1. **[File:Line]** - Suggestion
### Consider
1. **[File:Line]** - Optional improvement
### Positive Notes
- What was done well
### Verdict
- [ ] Approve
- [ ] Approve with comments
- [ ] Request changes
Project-Specific Checks
- Type hints on public functions
- Docstrings on public interfaces
- No hardcoded values (use config)
- Tests for new functionality
- Mock external services (Trello, GitHub APIs)
- Follow existing patterns in codebase
Quick Checks
# Find debug statements
git diff main...HEAD | grep -E "print\(|breakpoint|pdb"
# Find TODOs in changes
git diff main...HEAD --name-only | xargs grep -n "TODO\|FIXME"
# Check for secrets
git diff main...HEAD | grep -iE "password|secret|api.?key|token"