Review Prod Ready Skill banner
sakost sakost

Review Prod Ready Skill

Code Quality community

Description

A Claude Code skill that dispatches 7 specialized parallel reviewers for comprehensive production-readiness code review

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

review-prod-ready

A [Claude Code](https://code.claude.com) skill that dispatches **7 specialized parallel reviewers** to perform a comprehensive production-readiness code review. Each reviewer focuses on one dimension deeply — catching issues a single broad reviewer misses.

Why

A generic "review this code" prompt tends to produce shallow output: one reviewer tries to cover everything and ends up skimming across dimensions. This skill splits the review into 7 parallel tracks, each handled by a subagent primed with a nitpicking, skeptical mindset.

Observed gaps in single-reviewer setups that this skill addresses:

  • Useless tests (tests that would still pass if the implementation were broken)
  • type: ignore, noqa, eslint-disable directives hiding real bugs
  • DRY violations left unflagged
  • Partially-implemented plan items slipping through
  • Overly complex code accumulating bugs
  • Architecture-level issues missed while focused on line-level nits

Install

Personal install (available in all your projects):

git clone git@github.com:sakost/review-prod-ready-skill.git \
  ~/.claude/skills/review-prod-ready

Project-scoped install (only in the target repo):

git clone git@github.com:sakost/review-prod-ready-skill.git \
  .claude/skills/review-prod-ready

Usage

From inside Claude Code:

/review-prod-ready

Optionally pass a description or plan reference:

/review-prod-ready auth refactor per docs/auth-plan.md

The skill auto-detects the git range (merge-base with `main` or `master`) and injects the list of changed files into the prompt before dispatching the reviewers. Each reviewer reads the changed files in full, focuses on its dimension, and reports findings as:

  • Severity: Critical / Important / Minor
  • File:line reference
  • What's wrong
  • Why it matters
  • Suggested fix

The orchestrator aggregates findings into a single report with a final verdict (Yes / No / With fixes).

The 7 revie