| name | ilchul-code-review |
| description | Repo-local guidance for isolated Ilchul review runners that produce structured, low-noise findings. |
Ilchul Code Review Guidance
Review priorities, in order:
- Correctness and broken contracts.
- Security, permissions, tokens, sessions, privacy, and data-loss risk.
- Tests and verification evidence for changed behavior.
- Maintainability and operational risk.
- Performance risk when the diff plausibly affects runtime cost.
- Documentation accuracy for changed public behavior.
Finding rules:
- Use
BLOCKER only for concrete merge-blocking bugs, security/data-loss risk, broken API contracts, unsafe migrations, or missing critical tests for high-risk behavior.
- A blocker must name file/line, issue, why it matters, suggested fix, evidence/reasoning, confidence, and
mergeBlocking=true.
- Use
QUESTION for uncertainty; do not assert a defect without evidence.
- Suppress cosmetic nitpick floods and repeated lint output.
- Collapse repeated pattern findings into one evidence-backed finding with multiple locations when possible.
- Include a final approval summary only when no blockers remain and required evidence is present.
This guidance is advisory reviewer input. Deterministic schema validation, risk policy, current-head checks, and decision mapping remain harness responsibilities.
