review-merge-readiness
Request/execute structured code review: use after completing important tasks, at end of each execution batch, or before merge. Based on git diff range, compare against plan and requirements, output issue list by Critical/Important/Minor severity, and provide clear verdict on merge readiness. Trigger words: request code review, PR review, merge readiness, production readiness.
Best use case
review-merge-readiness is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Request/execute structured code review: use after completing important tasks, at end of each execution batch, or before merge. Based on git diff range, compare against plan and requirements, output issue list by Critical/Important/Minor severity, and provide clear verdict on merge readiness. Trigger words: request code review, PR review, merge readiness, production readiness.
Teams using review-merge-readiness should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/review-merge-readiness/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review-merge-readiness Compares
| Feature / Agent | review-merge-readiness | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Request/execute structured code review: use after completing important tasks, at end of each execution batch, or before merge. Based on git diff range, compare against plan and requirements, output issue list by Critical/Important/Minor severity, and provide clear verdict on merge readiness. Trigger words: request code review, PR review, merge readiness, production readiness.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Requesting Code Review (Structured Review: Requirements Alignment + Production Readiness) Goal: Make code review a repeatable process, not random comments. **Core principle: Review early, review often.** ## When Review is Required **Mandatory:** - After completing important features - After each batch in `workflow-execute-plans` ends (default 3 tasks per batch) - Before merging to main branch **Optional but valuable:** - When stuck (get a fresh perspective) - Before major refactoring (establish baseline first) - After fixing complex bugs (verify no new regressions) ## How to Initiate (Minimum Information Set) ### 1) Determine Review Scope (git SHA) Prefer using "baseline before plan/task started" as `BASE_SHA`: ```bash # Common approach: use main as baseline BASE_SHA=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master) HEAD_SHA=$(git rev-parse HEAD) ``` If you want to review just the most recent commit within a small task: ```bash BASE_SHA=$(git rev-parse HEAD~1) HEAD_SHA=$(git rev-parse HEAD) ``` ### 2) Prepare Review Basis (Plan / Requirements) Review must provide: - **WHAT_WAS_IMPLEMENTED**: What you just completed (1-3 bullet points) - **PLAN_OR_REQUIREMENTS**: Corresponding plan excerpt or requirements document path (e.g., `run_dir/03-plans/features/<feature_slug>-plan.md`) ### 3) Get diff (Evidence) ```bash git diff --stat "$BASE_SHA..$HEAD_SHA" git diff "$BASE_SHA..$HEAD_SHA" ``` ## Review Execution Methods (Choose One) ### Method A: Sub-Agent Review (if your system supports it) Use template: `review-merge-readiness/code-reviewer.md`, fill in placeholders and execute. ### Method B: Self Review (works without sub-agent) Check each item per template checklist and output same structured result (Strengths + Issues by severity + Verdict). ## Review Output Format (Must Be Structured) Output must include: - **Strengths**: Specific positives (at least 1) - **Issues**: Categorized by severity: - **Critical (Must Fix)**: Security/data loss/functionality bugs/would cause production incidents - **Important (Should Fix)**: Obviously poor architecture/missing error handling/test gaps/requirements misalignment - **Minor (Nice to Have)**: Style/small optimizations/documentation polish - **Assessment**: Merge readiness (Yes/No/With fixes) + 1-2 sentence technical reasoning Each Issue must include: - Location: `file:line` - What's wrong - Why it matters - How to fix (provide minimal change suggestion) ## Relationship with Other Review Skills - `review-clean-code`: More focused on "maintainability/cleanliness", suitable for deep code smell investigation - `review-react-best-practices`: More focused on React/Next.js performance patterns (waterfalls/bundle/re-renders). Use when the diff touches React UI, data fetching, or performance-sensitive areas. - This skill: More focused on "requirements alignment/production readiness/merge verdict" conclusion-oriented review If you just need a "can we merge?" verdict: use this skill. If you want a deep health check: additionally invoke `review-clean-code`.
Related Skills
review-seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see tool-programmatic-seo. For adding structured data, see tool-schema-markup.
review-react-best-practices
Review or refactor React / Next.js code for performance and reliability using a prioritized rule library (waterfalls, bundle size, server/client data fetching, re-renders, rendering). Use when writing React components, Next.js pages (App Router), optimizing bundle size, improving performance, or doing a React/Next.js performance review.
review-quality
Unified codebase quality review: merge readiness verdict + maintainability (Clean Code) + docs-vs-code consistency. Use for code review, quality check, refactor check, outdated docs check, or merge/production readiness.
review-doc-consistency
Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.
review-clean-code
Analyze code quality based on "Clean Code" principles. Identify naming, function size, duplication, over-engineering, and magic number issues with severity ratings and refactoring suggestions. Use when the user requests code quality checks, refactoring advice, Clean Code analysis, code smell detection, or mentions terms like code review, code quality, refactoring check.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
turbo-sdk
Complete Arweave Turbo ecosystem including client SDKs, core upload infrastructure, payment service backend, and CLI tools for permanent decentralized storage
terraform-best-practices
Comprehensive best practices for Terraform infrastructure as code from Anton Babenko's community guide
sveltekit-svelte5-tailwind-skill
Comprehensive integration skill for building sites with SvelteKit 2, Svelte 5, and Tailwind CSS v4
workflow-ship-faster
Ship Faster end-to-end workflow for small web apps (default: Next.js 16.1.1): idea/prototype → foundation gate → design-system.md → lightweight guardrails + docs → feature iteration → optional Supabase + Stripe → optional GitHub + Vercel deploy → optional AI-era SEO (sitemap/robots/llms.txt). Resumable, artifact-first under runs/ship-faster/ (or OpenSpec changes/). Trigger: ship/launch/deploy/production-ready MVP.
workflow-project-intake
Use when you need to clarify requirements and route to the right workflow (idea → executable input). Project intake + routing: help the user brainstorm and clarify intent, persist goal/context artifacts, then dispatch to the right workflow or step skill. Default route is workflow-ship-faster (Next.js 16.1.1) for idea/prototype→launch. Triggers: project kickoff, requirements clarification, brainstorm, ideas, discovery, intake.