Code review checklist
Review a code change for correctness, clarity, security, and tests using a structured checklist. Use when the user asks to review code, a diff, or a pull request.From its SKILL.md
npx -y skills add minagayid/Agents --skill code-review-checklistAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Code Review Checklist
Review a diff methodically and report findings ordered by severity.
Process
- Read the change end-to-end first to understand intent before nitpicking.
- Evaluate against the checklist below.
- Report as: Blocking (must fix), Non-blocking (should fix), Nits (optional).
For each finding give
file:line, the problem, and a concrete suggestion.
Checklist
Correctness
- Does it do what the PR claims? Edge cases, off-by-one, null/empty, error paths?
- Concurrency/race conditions; resource leaks (files, connections, listeners)?
Security
- Untrusted input validated/escaped? Injection (SQL/shell/HTML) avoided?
- Secrets not hard-coded or logged? AuthZ checks present on new endpoints?
Design & clarity
- Simplest solution that works? Any dead code or needless abstraction?
- Names, structure, and comments match the surrounding code?
Tests
- New behavior covered? Failure modes tested, not just the happy path?
- Tests deterministic and independent?
Ops
- Backward compatible? Migrations safe? Logging/metrics for new failure modes?
Guidelines
- Be specific and kind; critique the code, not the author.
- Distinguish facts ("this NPEs when
xis null") from preferences ("I'd name thistotal"). - Don't rubber-stamp — if you found nothing blocking, say what you checked.