ready-for-review

Verify code, sync branches, and fix PR descriptions before handoff.

4|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jcdendrite/claude-config --skill ready-for-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ready-for-review
Source: https://github.com/jcdendrite/claude-config/tree/main/claude/.claude/skills/ready-for-review
Command: npx skills add https://github.com/jcdendrite/claude-config --skill ready-for-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents code changes from being handed off to reviewers or CI-heavy collaboration until the branch is verified, reviewed, and synchronized with the base—reducing wasted cycles and surprise failures.

Core Features & Use Cases

  • Pre-handoff verification: Runs the repo’s defined test/lint/typecheck checks (or infers them from project config) and halts on failures.
  • Cumulative code review: Reviews the full cumulative diff between the PR base and HEAD (not just staged changes) to surface cross-commit issues.
  • PR hygiene enforcement: Verifies branch status (clean tree, pushed commits, in-sync with origin/base) and flags/fixes inaccurate or stale PR description content.
  • CI transparency (warn only): Surfaces PR check results so you can decide whether to wait for completion.
  • Loop-safe session control: Uses explicit marker activation/completion to avoid self-blocking when the gate iterates on fixes.

Quick Start

Ask your assistant to hand off the current feature branch to a human reviewer by triggering the ready-for-review gate.

Frequently Asked Questions about ready-for-review

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

FAQPage Schema
How do I verify a git pull request is ready for code review?

To verify a pull request is ready for code review, the gate checks for a clean working tree, syncs the branch with the base and remote, runs deterministic CI checks, and reviews the cumulative diff to prevent surprise failures during handoff.

What is a quality gate for PR handoff?

A PR handoff quality gate prevents code changes from reaching human reviewers until the branch is verified, fully reviewed for cross-commit issues, and synchronized with the base branch, reducing wasted review cycles and CI failures.

How do I enforce PR hygiene and sync branch state before shipping?

You enforce PR hygiene by verifying branch synchronization, ensuring the working tree is clean, and flagging or fixing inaccurate PR descriptions so the description matches the actual changes in the branch before shipping.

Can I run CI checks and linting automatically before a PR review?

Yes, the gate runs the repository's defined test, lint, and typecheck checks by inferring them from project configuration, halting the handoff process immediately if any deterministic checks fail.

When should I avoid using an automated PR review gate?

You should avoid using this automated review gate during active code iteration, when working directly on the default branch, or when you do not intend to ship or hand off the feature branch to human reviewers.

Does the ready-for-review gate block my workflow if CI is still running?

No, the gate surfaces PR check results via gh pr checks as a warning only, allowing you to transparently decide whether to wait for CI completion without hard-blocking the handoff process.