skills.rest
ambrovia
ambroviaOFFICIAL
Explore all skills by this author →
GitHub

ship

Verify code review and CI status before merging pull requests.

Updated Jun 12, 2026
Search Tags:#automation#git#workflow#pull request#deployment#ci
One-click install
npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill ship-ambrovia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/ambrovia/agent-skills-pipeline/tree/main/skills/ship
Command: npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill ship-ambrovia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent deployment readiness by enforcing a strict, multi-step verification process that ensures code is reviewed, tested, and ready for integration before a pull request is finalized.

Core Features & Use Cases

  • Automated Gatekeeping: Enforces mandatory code review verdicts and CI-green status before allowing a ship.
  • Atomic Workflow: Manages the commit, merge, and push lifecycle to ensure a clean, reliable main branch.
  • Use Case: Use this after completing a work package to automatically merge the latest main, run local verification, push your changes, and open a PR that is guaranteed to be CI-ready.

Quick Start

Execute the ship skill to finalize the current work package and open a pull request for review.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate pull request verification before merging to main?▼

Automating pull request verification involves enforcing mandatory code review verdicts and CI-green status before deployment. This skill manages that final gate by validating review status, merging the main branch, and ensuring CI passes for a merge-ready pull request.

What is the best way to ensure a clean git history during deployment?▼

Ensuring a clean git history during deployment requires an atomic workflow that manages the commit, merge, and push lifecycle. This approach guarantees a reliable main branch by enforcing pre-flight validation and a final clean-worktree attestation before integration.

How does automated CI-green status checking work for a merge-ready PR?▼

Automated CI-green status checking works by acting as a deployment gate that verifies continuous integration passes before finalizing a pull request. It automates the process of merging the latest main, running local verification, and pushing changes to guarantee CI readiness.

Can I enforce code review status checks before a git push?▼

Yes, you can enforce code review status checks before a push by applying strict quality gates. This skill automates gatekeeping by requiring mandatory review verdicts and passing CI status, preventing code from shipping until quality criteria are satisfied.

When do I need to run a final deployment gate for my git workflow?▼

You need to run a final deployment gate after completing a work package to finalize integration. It is required for software development workflows demanding strict adherence to quality gates, ensuring atomic commits and pre-flight validation before opening a pull request.

Related Skills

Explore More Software Engineering Skills→
jacexhjacexh

using-git-worktrees

Create isolated git worktrees with ignored directories and validated test baselines.

Community
Advanced
mckissingermckissinger
1

land-feature

Coordinate GitHub pull request landing workflows to safely merge verified features into the main branch.

Community
Advanced
intelli-verse-xintelli-verse-x
1

ivx-quality-gates

Automates quality gates for IntelliVerseX SDK projects in CI workflows.

Official
Advanced
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate