Use when reviewing code changes or pull requests. Provides the foundational rules, principles, and checklists for all code review agents.
Reference knowledge for code review agents. Load this skill to understand review scope, filtering rules, and quality standards.
This rule is non-negotiable for all review agents.
Review scope is LIMITED to lines that were ADDED or MODIFIED in the diff:
+ lines (additions) - reviewableSilent filtering: Skip pre-existing issues without mention. Do not say "I found X but it's pre-existing." Simply omit them entirely.
Verification: Before reporting any issue, confirm the line appears in the diff as an addition or modification.
All review agents use consistent output:
| File | Line | Type | Issue | Fix |
|---|---|---|---|---|
path/file.ts | 42 | Type | 10 words max | 10 words max |
Type labels:
Detailed checklists are available in references/:
code-quality-checklist.md - Clean code, SOLID, naming, architecturesecurity-checklist.md - OWASP-aligned security checkscontracts-checklist.md - API and type design checkstest-coverage-checklist.md - Test quality and coverage checksLoad specific checklists only when needed for that review type.
| Level | Criteria | Action |
|---|---|---|
| Critical | Data loss, security breach, production outage | Block merge |
| High | Core feature broken, significant bug | Should fix before merge |
| Medium | Edge case issues, maintainability | Consider fixing |
| Low | Minor improvements, style | Optional |
Issues must meet minimum confidence for their impact level:
| Impact | Min Confidence | Rationale |
|---|---|---|
| Critical (81-100) | 50% | Investigate even with moderate confidence |
| High (61-80) | 65% | Avoid false alarms on important issues |
| Medium (41-60) | 75% | Need high confidence to justify effort |
| Low (21-40) | 85% | Only report if very confident |
| Minor (0-20) | 95% | Only if nearly certain |