Code Review Checklist Generator skill for Claude and Codex
Builds a code review checklist your team will actually use: stack-specific checks grouped by category, ranked by severity, each with an example of what to…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a team needs a code review checklist tailored to their language, framework, and project type, with severity levels and examples. Do not use for reviewing a specific pull request, or writing a style guide and linter configuration. Related topics: coding, workflow, code.
What it will ask you for
- Language and framework (choose one: JavaScript/React, TypeScript/Next.js, Python/Django, Java/Spring, Go, Flutter/Dart, Ruby on Rails, Other)
- Project type (choose one: Frontend web app, Backend API, Mobile app, Full-stack, Library or package, DevOps or infrastructure)
- Team size (choose one: Solo, 2 to 5 people, 6 to 20 people, 20 or more)
- Categories to cover (choose any: Code quality and readability, Performance, Security vulnerabilities, Test coverage, Error handling, Documentation, Accessibility, Database queries, API design, Dependency management)
- Group by category (choose one: Yes, No)
- Include severity level (Critical or Major or Minor) (choose one: Yes, No)
- Add an example of what to look for per item (choose one: Yes, No)
How it works
- Write 25 to 40 checklist items, each naming a concrete stack-specific check a reviewer can verify from the diff alone.
- Group the items by the selected categories when requested and move runtime-only checks to a short Before merge list.
- Assign severity when requested, reserving Critical for merge blockers such as security, data loss, and broken builds.
- Add a one-line example or code smell per item when requested, so a new reviewer knows what the item looks like in code.
- Tailor the framing to team size: self-review questions for a solo developer, reviewer roles and blocking-comment rules for larger teams.
What you get
A Markdown checklist of 25 to 40 items, grouped by category when requested, each with optional severity and example, followed by a Before merge list and a two-line note on maintaining the checklist.
What it watches out for
- Writing generic items like check performance; a reviewer cannot act on them and will skip the whole list.
- Marking half the items Critical, which teaches the team that Critical does not mean blocking.
- Including checks that need a running system; a diff review cannot confirm them and the list loses credibility.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.