review-and-ship

Reviews branch changes for bugs and test coverage, then commits and opens pull requests on request.

3|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill review-and-ship-zanzythebar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-and-ship
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/review-and-ship
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill review-and-ship-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code without a structured review risks regressions, security issues, and untested behavior reaching production. This Skill enforces a disciplined review-and-ship workflow that validates changes against user intent before anything is committed or pushed. ## Core Features & Use Cases - Structured Branch Review: Gathers diffs against the base branch, uncommitted changes, and recent commits to review correctness, regressions, security, and intent fit. - Targeted Test Execution: Runs focused tests for changed behavior and flags coverage gaps when no tests exist. - Guarded Shipping: Creates Conventional Commits, pushes branches, and opens or updates pull requests only when the user explicitly approves. - Use Case: After finishing a feature branch, ask for a review-and-ship pass to catch critical issues, verify tests pass, and open a deduplicated PR with a clean commit history. ## Quick Start Review my current branch against the base branch, run the relevant tests, and open a pull request once I confirm the findings look good.

Frequently Asked Questions about review-and-ship

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

FAQPage Schema
How do I review a git branch before opening a pull request?

Diff the branch against the base branch, run targeted tests for changed behavior, and check for correctness, regressions, and security issues. This Skill automates that sequence and summarizes findings as critical, warning, or note before any commit or PR action.

How to create a pull request with the GitHub CLI?

Use gh pr create after pushing your branch, and verify readiness with gh pr checks to inspect CI status. The Skill deduplicates by branch before creating a PR and uses body files for newline-safe descriptions.

Does this workflow commit or push without my approval?

No. Commits, pushes, and pull request creation happen only when you explicitly request or approve them. The guardrails also respect jj-based workflows where available and never bypass failing pre-commit hooks.

What happens when no tests exist for changed code?

The workflow decides whether to add focused tests for the changed behavior or explicitly document the coverage gap. Critical issues found during review are fixed and affected tests re-run before finalizing.

Why use gh pr checks instead of GitHub Actions commands?

gh pr checks provides a consolidated view of all PR check statuses including names, states, and links, making it more reliable for judging PR readiness than querying individual workflow runs.