skills.rest
hack-ink
hack-inkOFFICIAL
Explore all skills by this author →
WebsiteGitHub

review-prepare

Execute the primary self-review gate on the actual diff before PR creation.

Updated Aug 27, 2026
Search Tags:#git#workflow#review#diff#code-review#pull-request#branch-readiness
One-click install
npx skills add https://github.com/hack-ink/codexlab --skill review-prepare
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-prepare
Source: https://github.com/hack-ink/codexlab/tree/main/.codex/skills/review-prepare
Command: npx skills add https://github.com/hack-ink/codexlab --skill review-prepare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use before creating or refreshing a PR head, including after review-repair changes the branch, to run the primary self-review gate on the actual diff. Wraps the shared review-loop mechanics for branch-readiness review and maps that result onto pre-PR go/no-go status.

Core Features & Use Cases

  • Wraps the shared review-loop to validate branch readiness on the actual diff.
  • Maps the review-loop outcome to a pre-PR go/no-go status to gate PR creation.
  • Works across typical development branches and linked plans.

Quick Start

Run review-prepare on the current branch to execute the primary self-review gate before PR creation.

Frequently Asked Questions about review-prepare

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

FAQPage Schema
How do I automate self-review on my git diff before creating a pull request?▼

Yes, you can enforce a code-review gate for branch readiness by running this Skill after review repairs change your branch. It re-executes the self-review against the actual diff to determine pre-PR go/no-go readiness and prevent PRs with unresolved review debt.

What is the best way to prevent unresolved code-review debt in a pull request?▼

The best way to prevent unresolved code-review debt in a pull request is to enforce a pre-PR readiness gate. This Skill maps review-loop outcomes to a stable status by requiring the reviewed head SHA and verifiable evidence before allowing PR creation.

Does this branch-readiness review work across multiple development branches and linked plans?▼

Yes, branch-readiness review works across typical development branches and linked plans. The Skill applies when preparing or refreshing a PR head after review repairs, ensuring consistent pre-PR go/no-go readiness validation wherever your workflow branches.

When should I run a pre-PR self-review gate on my code changes?▼

You should run a pre-PR self-review gate before creating or refreshing a PR head, including after review-repair changes the branch. This ensures the actual diff passes the primary self-review loop before you map the results to a go/no-go status.

Related Skills

Explore More Software Engineering Skills→
lvndrylvndry
47

pr-description

Generate PR titles and descriptions from diffs and branch context.

Community
Intermediate
victor-brechbillvictor-brechbill
1

merge-pr

Merge a prepared GitHub pull request via squash and clean up worktrees.

Official
Advanced
Elevaria-biaElevaria-bia

coderabbit-review

Automate CodeRabbit CLI reviews in WSL with severity-scored pass/fail outcomes.

Community
Advanced
redisreadredisread

check

Automate code review, issue triage, release gating, and quality audits.

Community
Advanced