Code Review
Perform a thorough, multi-dimensional code review on $ARGUMENTS.
Reference: Google Engineering Practices
Review Strategy
When conducting code reviews:
- Understand the change context (PR description, issue, commit messages)
- Verify functional correctness against requirements
- Scan for security vulnerabilities (OWASP Top 10)
- Evaluate performance implications
- Assess maintainability and code quality
- Validate test coverage
Dynamic Context
- Git status: !
git status --short 2>/dev/null - Recent changes: !
git diff --stat HEAD~3 2>/dev/null || echo "N/A" - Staged changes: !
git diff --cached --stat 2>/dev/null || echo "N/A"
References
| Topic | Reference | Use for |
|---|---|---|
| Review Dimensions | references/review-dimensions.md | Full 5-dimension review checklists (Correctness, Security, Performance, Maintainability, Architecture) with code examples |
| Output Format | references/output-format.md | Review target resolution, severity classification, report template, best practices |
| Anti-Patterns | references/anti-patterns.md | Code smells table, security anti-patterns, performance anti-patterns with examples |
Related Skills
- security-scan - Deep security audit
- mutation-test - Test quality assessment
- pr-summary - PR documentation
Resources
Guardrails
- Prefer measured evidence over blanket rules of thumb.
- Ask for explicit human approval before destructive data operations (drops/deletes/truncates).
Source: gr1m0h/dot — distributed by TomeVault.