Code Review Guideline
This skill provides language-agnostic principles for conducting effective code reviews.
When to Use This Skill
- •Reviewing pull requests
- •Providing constructive feedback
- •Setting up review standards for a team
- •Self-reviewing code before submission
Core Philosophy
Code review serves two purposes:
- •Quality Gate: Catch bugs, vulnerabilities, and design issues
- •Knowledge Sharing: Spread understanding across the team
Quick Reference
Review Priorities (Highest → Lowest)
- •Correctness: Does it work correctly?
- •Security: Any vulnerabilities?
- •Architecture: Does it follow project patterns?
- •Test Quality: Are tests valuable (not just present)?
- •Readability: Can others understand it?
- •Performance: Any obvious issues?
Test Quality Signals
Good Signs:
- •Tests verify behavior, not implementation
- •Tests use real objects where possible
- •Mocks only at external boundaries
- •Clear Arrange-Act-Assert structure
Warning Signs:
- •Tests verify method call counts
- •Tests break on refactoring
- •Every class has corresponding test file (London school smell)
- •Mock setup longer than actual test
Resources
- •
resources/review-checklist.md- General review checklist - •
resources/tdd-verification.md- TDD practice verification
Integration with Other Skills
- •good-test-principles: Detailed test quality criteria
- •clean-architecture: Architecture compliance checking