Code Reviewing Skill — Quick Reference
This skill provides operational checklists and prompts for structured code review across languages and stacks. Use it when the primary task is reviewing existing code rather than designing new systems.
Quick Reference
| Review Type |
Focus Areas |
Key Checklist |
When to Use |
| Security Review |
Auth, input validation, secrets, OWASP Top 10 |
software-security-appsec |
Security-critical code, API endpoints |
| Performance Review |
N+1 queries, algorithms, caching, hot paths |
DB queries, loops, memory allocation |
High-traffic features, bottlenecks |
| Correctness Review |
Logic, edge cases, error handling, tests |
Boundary conditions, null checks, retries |
Business logic, data transformations |
| Maintainability Review |
Naming, complexity, duplication, readability |
Function length, naming clarity, DRY |
Complex modules, shared code |
| Test Review |
Coverage, edge cases, flakiness, assertions |
Test quality, missing scenarios |
New features, refactors |
| Frontend Review |
Accessibility, responsive design, performance |
frontend-review.md |
UI/UX changes |
| Backend Review |
API design, error handling, database patterns |
api-review.md |
API endpoints, services |
| Blockchain Review |
Reentrancy, access control, gas optimization |
crypto-review.md |
Smart contracts, DeFi protocols |
Specialized: .NET/EF Core Crypto Integration
Skip unless reviewing C#/.NET crypto/fintech services using Entity Framework Core.
For C#/.NET crypto/fintech services using Entity Framework Core, see:
- resources/dotnet-efcore-crypto-rules.md — Complete review rules (correctness, security, async, EF Core, tests, MRs)
Key rules summary:
- Review only new/modified code in the MR
- Use
decimal for financial values, UTC for dates
- Follow
CC-SEC-03 (no secrets in code) and CC-OBS-02 (no sensitive data in logs)
- Async for I/O, pass
CancellationToken, avoid .Result/.Wait() (see CC-ERR-04, CC-FLOW-03)
- EF Core:
AsNoTracking for reads, avoid N+1, no dynamic SQL
Result<T> pattern for explicit success/fail
When to Use This Skill
Invoke this skill when the user asks to:
- Review a pull request or diff for issues
- Audit code for security vulnerabilities or injection risks
- Improve readability, structure, and maintainability
- Suggest targeted refactors without changing behavior
- Validate tests and edge-case coverage
Decision Tree: Selecting Review Mode
Code review task: [What to Focus On?]
├─ Security-critical changes?
│ ├─ Auth/access control → Security Review (OWASP, auth patterns)
│ ├─ User input handling → Input validation, XSS, SQL injection
│ └─ Smart contracts → Blockchain Review (reentrancy, access control)
│
├─ Performance concerns?
│ ├─ Database queries → Check for N+1, missing indexes
│ ├─ Loops/algorithms → Complexity analysis, caching
│ └─ API response times → Profiling, lazy loading
│
├─ Correctness issues?
│ ├─ Business logic → Edge cases, error handling, tests
│ ├─ Data transformations → Boundary conditions, null checks
│ └─ Integration points → Retry logic, timeouts, fallbacks
│
├─ Maintainability problems?
│ ├─ Complex code → Naming, function length, duplication
│ ├─ Hard to understand → Comments, abstractions, clarity
│ └─ Technical debt → Refactoring suggestions
│
├─ Test coverage gaps?
│ ├─ New features → Happy path + error cases
│ ├─ Refactors → Regression tests
│ └─ Bug fixes → Reproduction tests
│
└─ Stack-specific review?
├─ Frontend → [frontend-review.md](templates/web-frontend/frontend-review.md)
├─ Backend → [api-review.md](templates/backend-api/api-review.md)
├─ Mobile → [mobile-review.md](templates/mobile/mobile-review.md)
├─ Infrastructure → [infrastructure-review.md](templates/infrastructure/infrastructure-review.md)
└─ Blockchain → [crypto-review.md](templates/blockchain/crypto-review.md)
Multi-Mode Reviews:
For complex PRs, apply multiple review modes sequentially:
- Security first (P0/P1 issues)
- Correctness (logic, edge cases)
- Performance (if applicable)
- Maintainability (P2/P3 suggestions)
Async Review Workflows (Dec 2025)
Timezone-Friendly Reviews
| Practice |
Implementation |
| Review windows |
Define 4-hour overlap windows |
| Review rotation |
Assign reviewers across timezones |
| Async communication |
Use PR comments, not DMs |
| Review SLAs |
24-hour initial response, 48-hour completion |
Non-Blocking Reviews
PR Submitted -> Auto-checks (CI) -> Async Review -> Merge
| | |
Author continues If green, Reviewer comments
on other work queue for when available
review
Anti-patterns:
- Synchronous review meetings for routine PRs
- Blocking on reviewer availability for non-critical changes
- Single reviewer bottleneck
Review Prioritization Matrix
| Priority |
Criteria |
SLA |
| P0 |
Security fix, production incident |
4 hours |
| P1 |
Bug fix, blocking dependency |
24 hours |
| P2 |
Feature work, tech debt |
48 hours |
| P3 |
Documentation, refactoring |
72 hours |
Optional: AI/Automation Extensions
Note: AI-assisted review tools. Human review remains authoritative.
AI Review Assistants
| Tool |
Use Case |
Limitation |
| GitHub Copilot PR |
Summary, suggestions |
May miss context |
| CodeRabbit |
Automated comments |
Requires human validation |
| Graphite |
PR stacking, review flow |
Process, not content |
AI assistant rules:
- AI suggestions are advisory only
- Human reviewer approves/rejects
- AI cannot bypass security review
- AI findings require manual verification
AI Review Checklist
Simplicity and Complexity Control
- Prefer existing, battle-tested libraries over bespoke implementations when behavior is identical.
- Flag avoidable complexity early: remove dead/commented-out code, collapse duplication, and extract single-responsibility helpers.
- Call out premature optimization; favor clarity and measured, evidence-based tuning.
- Encourage incremental refactors alongside reviews to keep modules small, predictable, and aligned to standards.
Operational Playbooks
Shared Foundation
Code Review Specific
- resources/operational-playbook.md — Review scope rules, severity ratings (P0-P3), checklists, modes, and PR workflow patterns
Navigation
Resources
- resources/operational-playbook.md
- resources/review-checklist-comprehensive.md
- resources/implementing-effective-code-reviews-checklist.md
- resources/looks-good-to-me-checklist.md
- resources/automation-tools.md
- resources/dotnet-efcore-crypto-rules.md
- resources/psychological-safety-guide.md
Templates
- templates/core/pull-request-description-template.md
- templates/core/review-checklist-judgment.md
- templates/core/review-comment-guidelines.md
- templates/backend-api/api-review.md
- templates/web-frontend/frontend-review.md
- templates/mobile/mobile-review.md
- templates/infrastructure/infrastructure-review.md
- templates/blockchain/crypto-review.md
- templates/data-ml/data-pipeline-review.md
- templates/data-ml/experiment-tracking-review.md
- templates/data-ml/ml-model-review.md
- templates/data-ml/ml-deployment-review.md
Data
1---2name: software-code-review3description: Patterns, checklists, and templates for systematic code review with a focus on correctness, security, readability, performance, and maintainability.4---5
6# Code Reviewing Skill — Quick Reference
7
8This skill provides operational checklists and prompts for structured code review across languages and stacks. Use it when the primary task is reviewing existing code rather than designing new systems.
9
10---
11
12## Quick Reference
13
14| Review Type | Focus Areas | Key Checklist | When to Use |
15|-------------|-------------|---------------|-------------|
16| Security Review | Auth, input validation, secrets, OWASP Top 10 | [software-security-appsec](../software-security-appsec/SKILL.md) | Security-critical code, API endpoints |
17| Performance Review | N+1 queries, algorithms, caching, hot paths | DB queries, loops, memory allocation | High-traffic features, bottlenecks |
18| Correctness Review | Logic, edge cases, error handling, tests | Boundary conditions, null checks, retries | Business logic, data transformations |
19| Maintainability Review | Naming, complexity, duplication, readability | Function length, naming clarity, DRY | Complex modules, shared code |
20| Test Review | Coverage, edge cases, flakiness, assertions | Test quality, missing scenarios | New features, refactors |
21| Frontend Review | Accessibility, responsive design, performance | [frontend-review.md](templates/web-frontend/frontend-review.md) | UI/UX changes |
22| Backend Review | API design, error handling, database patterns | [api-review.md](templates/backend-api/api-review.md) | API endpoints, services |
23| Blockchain Review | Reentrancy, access control, gas optimization | [crypto-review.md](templates/blockchain/crypto-review.md) | Smart contracts, DeFi protocols |
24
25---
26
27## Specialized: .NET/EF Core Crypto Integration
28
29Skip unless reviewing C#/.NET crypto/fintech services using Entity Framework Core.
30
31For C#/.NET crypto/fintech services using Entity Framework Core, see:
32
33- [resources/dotnet-efcore-crypto-rules.md](resources/dotnet-efcore-crypto-rules.md) — Complete review rules (correctness, security, async, EF Core, tests, MRs)
34
35**Key rules summary:**
36
37- Review only new/modified code in the MR
38- Use `decimal` for financial values, UTC for dates
39- Follow `CC-SEC-03` (no secrets in code) and `CC-OBS-02` (no sensitive data in logs)
40- Async for I/O, pass `CancellationToken`, avoid `.Result`/`.Wait()` (see `CC-ERR-04`, `CC-FLOW-03`)
41- EF Core: `AsNoTracking` for reads, avoid N+1, no dynamic SQL
42- `Result<T>` pattern for explicit success/fail
43
44---
45
46## When to Use This Skill
47
48Invoke this skill when the user asks to:
49
50- Review a pull request or diff for issues
51- Audit code for security vulnerabilities or injection risks
52- Improve readability, structure, and maintainability
53- Suggest targeted refactors without changing behavior
54- Validate tests and edge-case coverage
55
56## Decision Tree: Selecting Review Mode
57
58```text
59Code review task: [What to Focus On?]
60 ├─ Security-critical changes?
61 │ ├─ Auth/access control → Security Review (OWASP, auth patterns)
62 │ ├─ User input handling → Input validation, XSS, SQL injection
63 │ └─ Smart contracts → Blockchain Review (reentrancy, access control)
64 │
65 ├─ Performance concerns?
66 │ ├─ Database queries → Check for N+1, missing indexes
67 │ ├─ Loops/algorithms → Complexity analysis, caching
68 │ └─ API response times → Profiling, lazy loading
69 │
70 ├─ Correctness issues?
71 │ ├─ Business logic → Edge cases, error handling, tests
72 │ ├─ Data transformations → Boundary conditions, null checks
73 │ └─ Integration points → Retry logic, timeouts, fallbacks
74 │
75 ├─ Maintainability problems?
76 │ ├─ Complex code → Naming, function length, duplication
77 │ ├─ Hard to understand → Comments, abstractions, clarity
78 │ └─ Technical debt → Refactoring suggestions
79 │
80 ├─ Test coverage gaps?
81 │ ├─ New features → Happy path + error cases
82 │ ├─ Refactors → Regression tests
83 │ └─ Bug fixes → Reproduction tests
84 │
85 └─ Stack-specific review?
86 ├─ Frontend → [frontend-review.md](templates/web-frontend/frontend-review.md)
87 ├─ Backend → [api-review.md](templates/backend-api/api-review.md)
88 ├─ Mobile → [mobile-review.md](templates/mobile/mobile-review.md)
89 ├─ Infrastructure → [infrastructure-review.md](templates/infrastructure/infrastructure-review.md)
90 └─ Blockchain → [crypto-review.md](templates/blockchain/crypto-review.md)
91```
92
93**Multi-Mode Reviews:**
94
95For complex PRs, apply multiple review modes sequentially:
96
971. **Security first** (P0/P1 issues)
982. **Correctness** (logic, edge cases)
993. **Performance** (if applicable)
1004. **Maintainability** (P2/P3 suggestions)
101
102---
103
104## Async Review Workflows (Dec 2025)
105
106### Timezone-Friendly Reviews
107
108| Practice | Implementation |
109|----------|----------------|
110| Review windows | Define 4-hour overlap windows |
111| Review rotation | Assign reviewers across timezones |
112| Async communication | Use PR comments, not DMs |
113| Review SLAs | 24-hour initial response, 48-hour completion |
114
115### Non-Blocking Reviews
116
117```text
118PR Submitted -> Auto-checks (CI) -> Async Review -> Merge
119 | | |
120 Author continues If green, Reviewer comments
121 on other work queue for when available
122 review
123```
124
125**Anti-patterns:**
126
127- Synchronous review meetings for routine PRs
128- Blocking on reviewer availability for non-critical changes
129- Single reviewer bottleneck
130
131### Review Prioritization Matrix
132
133| Priority | Criteria | SLA |
134|----------|----------|-----|
135| P0 | Security fix, production incident | 4 hours |
136| P1 | Bug fix, blocking dependency | 24 hours |
137| P2 | Feature work, tech debt | 48 hours |
138| P3 | Documentation, refactoring | 72 hours |
139
140---
141
142### Optional: AI/Automation Extensions
143
144> **Note**: AI-assisted review tools. Human review remains authoritative.
145
146#### AI Review Assistants
147
148| Tool | Use Case | Limitation |
149|------|----------|------------|
150| GitHub Copilot PR | Summary, suggestions | May miss context |
151| CodeRabbit | Automated comments | Requires human validation |
152| Graphite | PR stacking, review flow | Process, not content |
153
154**AI assistant rules:**
155
156- AI suggestions are advisory only
157- Human reviewer approves/rejects
158- AI cannot bypass security review
159- AI findings require manual verification
160
161#### AI Review Checklist
162
163- [ ] AI suggestions validated against codebase patterns
164- [ ] AI-flagged issues manually confirmed
165- [ ] False positives documented for tool improvement
166- [ ] Human reviewer explicitly approved
167
168---
169
170## Simplicity and Complexity Control
171
172- Prefer existing, battle-tested libraries over bespoke implementations when behavior is identical.
173- Flag avoidable complexity early: remove dead/commented-out code, collapse duplication, and extract single-responsibility helpers.
174- Call out premature optimization; favor clarity and measured, evidence-based tuning.
175- Encourage incremental refactors alongside reviews to keep modules small, predictable, and aligned to standards.
176
177---
178
179## Operational Playbooks
180
181**Shared Foundation**
182
183- [../software-clean-code-standard/resources/clean-code-standard.md](../software-clean-code-standard/resources/clean-code-standard.md) - Canonical clean code rules (`CC-*`) for citation in reviews
184- Legacy playbook: [../software-clean-code-standard/resources/code-quality-operational-playbook.md](../software-clean-code-standard/resources/code-quality-operational-playbook.md) - `RULE-01`–`RULE-13`, refactoring decision trees, and design patterns
185
186**Code Review Specific**
187
188- [resources/operational-playbook.md](resources/operational-playbook.md) — Review scope rules, severity ratings (P0-P3), checklists, modes, and PR workflow patterns
189
190## Navigation
191
192**Resources**
193- [resources/operational-playbook.md](resources/operational-playbook.md)
194- [resources/review-checklist-comprehensive.md](resources/review-checklist-comprehensive.md)
195- [resources/implementing-effective-code-reviews-checklist.md](resources/implementing-effective-code-reviews-checklist.md)
196- [resources/looks-good-to-me-checklist.md](resources/looks-good-to-me-checklist.md)
197- [resources/automation-tools.md](resources/automation-tools.md)
198- [resources/dotnet-efcore-crypto-rules.md](resources/dotnet-efcore-crypto-rules.md)
199- [resources/psychological-safety-guide.md](resources/psychological-safety-guide.md)
200
201**Templates**
202- [templates/core/pull-request-description-template.md](templates/core/pull-request-description-template.md)
203- [templates/core/review-checklist-judgment.md](templates/core/review-checklist-judgment.md)
204- [templates/core/review-comment-guidelines.md](templates/core/review-comment-guidelines.md)
205- [templates/backend-api/api-review.md](templates/backend-api/api-review.md)
206- [templates/web-frontend/frontend-review.md](templates/web-frontend/frontend-review.md)
207- [templates/mobile/mobile-review.md](templates/mobile/mobile-review.md)
208- [templates/infrastructure/infrastructure-review.md](templates/infrastructure/infrastructure-review.md)
209- [templates/blockchain/crypto-review.md](templates/blockchain/crypto-review.md)
210- [templates/data-ml/data-pipeline-review.md](templates/data-ml/data-pipeline-review.md)
211- [templates/data-ml/experiment-tracking-review.md](templates/data-ml/experiment-tracking-review.md)
212- [templates/data-ml/ml-model-review.md](templates/data-ml/ml-model-review.md)
213- [templates/data-ml/ml-deployment-review.md](templates/data-ml/ml-deployment-review.md)
214
215**Data**
216- [data/sources.json](data/sources.json) — Curated external references
217- Shared checklists: [../software-clean-code-standard/templates/checklists/secure-code-review-checklist.md](../software-clean-code-standard/templates/checklists/secure-code-review-checklist.md), [../software-clean-code-standard/templates/checklists/backend-api-review-checklist.md](../software-clean-code-standard/templates/checklists/backend-api-review-checklist.md)