skills.rest
The-Vibe-Company
The-Vibe-CompanyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ship-pr-dev

Prepares branches into human-reviewable pull requests with verification, review gates, and CI monitoring.

2.4k|292|Updated Feb 7, 2026
Search Tags:#verification#Automation#ci#Git Workflow#gitHub#Code review#Pull request
One-click install
npx skills add https://github.com/The-Vibe-Company/companion --skill ship-pr-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-pr-dev
Source: https://github.com/The-Vibe-Company/companion/tree/main/.agents/skills/ship-pr-dev
Command: npx skills add https://github.com/The-Vibe-Company/companion --skill ship-pr-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Shipping a branch as a merge-ready pull request involves many error-prone steps: cleaning up unrelated changes, running the right checks, getting an independent code review, writing a proper PR description, and waiting for CI to go green on the latest commit. This Skill automates that entire delivery loop while enforcing strict safety rules, so a human reviewer receives a PR they can confidently merge.

Core Features & Use Cases

  • End-to-end PR delivery: Collects branch context, runs deterministic verification (lint, typecheck, tests, build), commits with commitzen messages, pushes, creates or updates the PR, and waits until every visible CI check is green on the latest pushed SHA.
  • Credit-aware worker delegation: Routes bounded implementation and review work to host-native workers (Codex, Claude Code, OpenCode) with tiered budgets, a single-writer rule, and one independent review-code-dev gate instead of duplicated review passes.
  • Strict readiness gates: Never merges, never force-pushes, never bypasses hooks, protects unrelated user work, blocks on unresolved P0/P1 findings or red CI, and runs a report-only learning pass before handoff.
  • Use Case: You finished a backend fix on a feature branch and say "ship this as a PR." The Skill verifies the change, runs the review gate, fixes findings, pushes, opens the PR, iterates on CI failures, and returns the PR URL only when everything is green.

Quick Start

Ask the assistant to ship the current branch as a pull request against main without merging it.

Frequently Asked Questions about ship-pr-dev

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

FAQPage Schema
How do I ship a branch as a pull request automatically?▼

Invoke the ship-pr-dev skill with a request like "ship this branch as a PR." It collects branch context, runs local verification, performs one independent review gate, commits and pushes, creates or updates the PR, and waits until all visible CI checks are green on the latest commit.

How to fix failing CI on an existing pull request?▼

Use the update-pr mode: the skill reads failing CI logs, identifies the first causal error, applies a scoped fix, reruns the matching local check, pushes, and rebuilds the CI inventory. It stops after three distinct corrections for one check and never disables or bypasses checks.

Can it create a PR without including unrelated local changes?▼

Yes. The skill separates in-scope changes from unrelated dirty files, stages only intentional paths, and refuses broad staging. If unrelated work cannot be separated safely, it stops and asks rather than committing or discarding your work.

Does the skill merge the pull request or force-push?▼

No. It never merges, enables auto-merge, force-pushes, hard-resets, or rewrites public history unless you explicitly request that exact operation. The final handoff is a PR that is ready for a human to merge.

What review process runs before the PR is marked ready?▼

A single review-code-dev gate runs in quick, standard, or deep mode depending on risk, with lenses such as frontend or security passed into the same run. P0 and P1 findings must be fixed, and a second full review is capped at two runs.

When should I use local-only mode instead of shipping?▼

Use prepare or local-handoff mode when you want cleanup, verification, and review evidence without pushing or opening a PR. The skill returns whether the branch is merge-ready and what remains, with no remote mutation.

Related Skills

Explore More Software Engineering Skills→
tachfineamnaytachfineamnay

Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Community
Intermediate
yusaduymazyusaduymaz

gsd-ship

Push verified branches and open pull requests for merge tracking.

Community
Advanced
azmiariffarisazmiariffaris

requesting-code-review

Automate pre-commit verification with static security scans and quality gates.

Community
Advanced
sparkfabriksparkfabrik
3

glab

Automate GitLab issues, merge requests, CI pipelines, and repository operations via the glab CLI.

Official
Intermediate