Every comment must be clearly marked as blocking or advisory.
Prefix
Meaning
Author must
[blocking]
Must be resolved before merge
Fix or discuss with reviewer
[advisory]
Suggestion, optional improvement
Address or explicitly acknowledge
[question]
Seeking understanding, not a change request
Answer the question
Examples:
[blocking] This query is not parameterized — SQL injection risk on line 47.
[advisory] This helper could be extracted to a utility function for reuse.
[question] Why is this retry limit set to 3?
Review Focus (Priority Order)
Correctness — does it do what it claims? Are edge cases handled?
Test coverage — is new behavior tested? Are tests testing behavior?
Design — right abstraction? Fits existing patterns?
Style — only flag if linting tools don't catch it
Do not comment on style a linter would catch. Do not re-litigate decisions in docs/adr/DECISIONS.md unless new risk is identified. Do not review from memory — verify against current file contents.
1---2name: cheneeheng-agent-skills-code-review3description: Code Review4---56# Code Review78Every comment must be clearly marked as **blocking** or **advisory**.910| Prefix | Meaning | Author must |11|--------|---------|-------------|12| `[blocking]` | Must be resolved before merge | Fix or discuss with reviewer |13| `[advisory]` | Suggestion, optional improvement | Address or explicitly acknowledge |14| `[question]` | Seeking understanding, not a change request | Answer the question |1516Examples:17```18[blocking] This query is not parameterized — SQL injection risk on line 47.1920[advisory] This helper could be extracted to a utility function for reuse.2122[question] Why is this retry limit set to 3?23```2425## Review Focus (Priority Order)26271. **Correctness** — does it do what it claims? Are edge cases handled?282. **Security** — injection risks, secrets exposure, input validation gaps293. **Test coverage** — is new behavior tested? Are tests testing behavior?304. **Design** — right abstraction? Fits existing patterns?315. **Style** — only flag if linting tools don't catch it3233Do not comment on style a linter would catch. Do not re-litigate decisions in `docs/adr/DECISIONS.md` unless new risk is identified. Do not review from memory — verify against current file contents.3435---36> Source: [cheneeheng/agent-skills](https://github.com/cheneeheng/agent-skills) — distributed by [TomeVault](https://tomevault.io).37<!-- tomevault:4.0:skill_md:2026-05-22 -->
Run npx skillmds@latest add tomevault-io/cheneeheng-agent-skills-code-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Code Review It is listed under AI & ML on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io