code-review-checklist

Reviews code changes against a phased pass/fail checklist with stack-specific extensions.

2|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Arasz/ai-badger --skill code-review-checklist-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-checklist
Source: https://github.com/Arasz/ai-badger/tree/main/features/common/skills/code-review-checklist
Command: npx skills add https://github.com/Arasz/ai-badger --skill code-review-checklist-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code reviews often rely on reviewer intuition, producing inconsistent feedback and missed defects. This Skill replaces impressions with a structured, aviation-style preflight checklist of concrete pass/fail checks, so every review covers the same critical ground regardless of reviewer experience. ## Core Features & Use Cases - Sequential phased checklist: Nine phases from pre-takeoff gates (build, tests, lint, secrets) through architecture, security, concurrency, contract alignment, accessibility, and post-merge verification, where Phase 1 gates everything else. - Stack-specific extensions: Additional check items for dotnet, react, ts, azure, cosmos, and mcp projects are merged into the relevant phases automatically based on project configuration. - Structured findings format: Every FAIL is reported with severity, location, evidence, impact, fix, and false-positive notes, so findings are actionable rather than vague. - Use Case: Before approving a pull request that touches both a .NET API and a React frontend, run the checklist to verify layering rules, test anti-patterns, client-server contract alignment, and accessibility items, then sign off only when all phases pass. ## Quick Start Review the current pull request using the code review checklist and report every failing item with its severity, location, and suggested fix.

Frequently Asked Questions about code-review-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request with a structured checklist?

Walk the checklist phases sequentially, verifying each item against the actual code and marking PASS or FAIL. Phase 1 gates everything: build, tests, lint, and secrets must pass before proceeding. Report every FAIL with severity, location, evidence, impact, and a suggested fix.

What does a code review checklist check before approving a PR?

It covers pre-takeoff gates (build, tests, lint, hardcoded secrets), architecture and layering, TDD compliance and test anti-patterns, security, concurrency and idempotency, client-server contract alignment, accessibility, and post-merge verification.

Does the checklist support stack-specific checks for dotnet or react?

Yes. Extensions for dotnet, react, ts, azure, cosmos, and mcp merge additional items into the relevant phases based on the project's configured stacks, such as DI registration checks for dotnet or react-query patterns for react.

When should I not use this code review checklist?

Use plan-review for plan or spec feasibility, frontend-code-review for frontend architecture deep-dives, comprehensive-code-review for full milestone methodology, and requesting-code-review for pre-commit security scans. This checklist targets concrete pass/fail verification of code changes.

Why does the checklist flag tests that always pass?

Tests with no assertion, always-true assertions, un-awaited async assertions, or swallowed exceptions report green while verifying nothing. Each such pattern is an automatic FAIL and the test must be rewritten or deleted, not argued down.