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 |
.NET/EF Core Crypto Integration
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
- No secrets in code, no sensitive data in logs
- Async for I/O, pass
CancellationToken, no .Result/.Wait()
- 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)
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/automation-tools.md
- resources/dotnet-efcore-crypto-rules.md
- resources/psychological-safety-guide.md
Templates
- 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
- data/sources.json — Curated external references
1---2name: software-code-review-23description: Patterns, checklists, and templates for systematic code review with a focus on correctness, security, readability, performance, and maintainability.4---56# Code Reviewing Skill — Quick Reference78This 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.910---1112## Quick Reference1314| 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 |2425---2627## .NET/EF Core Crypto Integration2829For C#/.NET crypto/fintech services using Entity Framework Core, see:3031- [resources/dotnet-efcore-crypto-rules.md](resources/dotnet-efcore-crypto-rules.md) — Complete review rules (correctness, security, async, EF Core, tests, MRs)3233**Key rules summary:**3435- Review only new/modified code in the MR36- Use `decimal` for financial values, UTC for dates37- No secrets in code, no sensitive data in logs38- Async for I/O, pass `CancellationToken`, no `.Result`/`.Wait()`39- EF Core: `AsNoTracking` for reads, avoid N+1, no dynamic SQL40- `Result<T>` pattern for explicit success/fail4142---4344## When to Use This Skill4546Invoke this skill when the user asks to:4748- Review a pull request or diff for issues49- Audit code for security vulnerabilities or injection risks50- Improve readability, structure, and maintainability51- Suggest targeted refactors without changing behavior52- Validate tests and edge-case coverage5354## Decision Tree: Selecting Review Mode5556```text57Code review task: [What to Focus On?]58 ├─ Security-critical changes?59 │ ├─ Auth/access control → Security Review (OWASP, auth patterns)60 │ ├─ User input handling → Input validation, XSS, SQL injection61 │ └─ Smart contracts → Blockchain Review (reentrancy, access control)62 │63 ├─ Performance concerns?64 │ ├─ Database queries → Check for N+1, missing indexes65 │ ├─ Loops/algorithms → Complexity analysis, caching66 │ └─ API response times → Profiling, lazy loading67 │68 ├─ Correctness issues?69 │ ├─ Business logic → Edge cases, error handling, tests70 │ ├─ Data transformations → Boundary conditions, null checks71 │ └─ Integration points → Retry logic, timeouts, fallbacks72 │73 ├─ Maintainability problems?74 │ ├─ Complex code → Naming, function length, duplication75 │ ├─ Hard to understand → Comments, abstractions, clarity76 │ └─ Technical debt → Refactoring suggestions77 │78 ├─ Test coverage gaps?79 │ ├─ New features → Happy path + error cases80 │ ├─ Refactors → Regression tests81 │ └─ Bug fixes → Reproduction tests82 │83 └─ Stack-specific review?84 ├─ Frontend → [frontend-review.md](templates/web-frontend/frontend-review.md)85 ├─ Backend → [api-review.md](templates/backend-api/api-review.md)86 ├─ Mobile → [mobile-review.md](templates/mobile/mobile-review.md)87 ├─ Infrastructure → [infrastructure-review.md](templates/infrastructure/infrastructure-review.md)88 └─ Blockchain → [crypto-review.md](templates/blockchain/crypto-review.md)89```9091**Multi-Mode Reviews:**9293For complex PRs, apply multiple review modes sequentially:94951. **Security first** (P0/P1 issues)962. **Correctness** (logic, edge cases)973. **Performance** (if applicable)984. **Maintainability** (P2/P3 suggestions)99100---101102## Simplicity and Complexity Control103104- Prefer existing, battle-tested libraries over bespoke implementations when behavior is identical.105- Flag avoidable complexity early: remove dead/commented-out code, collapse duplication, and extract single-responsibility helpers.106- Call out premature optimization; favor clarity and measured, evidence-based tuning.107- Encourage incremental refactors alongside reviews to keep modules small, predictable, and aligned to standards.108109---110111## Operational Playbooks112113**Shared Foundation**114115- [../../_shared/resources/code-quality-operational-playbook.md](../../_shared/resources/code-quality-operational-playbook.md) — Canonical coding rules (RULE-01 to RULE-13), refactoring decision trees, design patterns, and LLM-generated code review protocol116117**Code Review Specific**118119- [resources/operational-playbook.md](resources/operational-playbook.md) — Review scope rules, severity ratings (P0-P3), checklists, modes, and PR workflow patterns120121## Navigation122123**Resources**124- [resources/operational-playbook.md](resources/operational-playbook.md)125- [resources/review-checklist-comprehensive.md](resources/review-checklist-comprehensive.md)126- [resources/automation-tools.md](resources/automation-tools.md)127- [resources/dotnet-efcore-crypto-rules.md](resources/dotnet-efcore-crypto-rules.md)128- [resources/psychological-safety-guide.md](resources/psychological-safety-guide.md)129130**Templates**131- [templates/backend-api/api-review.md](templates/backend-api/api-review.md)132- [templates/web-frontend/frontend-review.md](templates/web-frontend/frontend-review.md)133- [templates/mobile/mobile-review.md](templates/mobile/mobile-review.md)134- [templates/infrastructure/infrastructure-review.md](templates/infrastructure/infrastructure-review.md)135- [templates/blockchain/crypto-review.md](templates/blockchain/crypto-review.md)136- [templates/data-ml/data-pipeline-review.md](templates/data-ml/data-pipeline-review.md)137- [templates/data-ml/experiment-tracking-review.md](templates/data-ml/experiment-tracking-review.md)138- [templates/data-ml/ml-model-review.md](templates/data-ml/ml-model-review.md)139- [templates/data-ml/ml-deployment-review.md](templates/data-ml/ml-deployment-review.md)140141**Data**142- [data/sources.json](data/sources.json) — Curated external references