WannaBuild: Ship Phase

Create PRs referencing spec artifacts and monitor CI checks until merge.

2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/gl11tchy/wannabuild --skill wannabuild-ship-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: WannaBuild: Ship Phase
Source: https://github.com/gl11tchy/wannabuild/tree/main/skills/ship
Command: npx skills add https://github.com/gl11tchy/wannabuild --skill wannabuild-ship-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ship Phase automates the creation of PRs referencing spec artifacts and monitors CI to ensure all checks pass before merge, reducing manual handoff and merge risk.

Core Features & Use Cases

  • PR Craftsman creates PRs that reference the spec artifacts
  • CI Guardian monitors CI checks and verifies integration tests in the pipeline
  • Use Case: After a successful review, the Ship phase automatically triggers PR creation and CI monitoring to reach merge readiness.

Quick Start

Invoke the ship phase after review approval to automatically create a PR, reference specs, and monitor CI until merge readiness.

Frequently Asked Questions about WannaBuild: Ship Phase

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

FAQPage Schema
How do I automate PR creation and CI monitoring for merge readiness?

To automate pull request creation and CI monitoring, invoke the ship phase after review approval to automatically generate PRs referencing spec artifacts and track CI checks until merge readiness.

What's the best way to ensure CI checks pass before merging a pull request?

Ensuring CI checks pass before merge requires monitoring the pipeline automatically; the CI Guardian component verifies integration tests and checks to reduce manual handoff and merge risk.

Do I need specific artifacts to automate pull request workflows?

Yes, automating pull request workflows requires access to spec artifacts located at .wannabuild/spec to properly reference design, requirements, and task details in the PR.

When should I trigger the ship phase in a software development workflow?

Trigger the ship phase after a successful review approval to automatically initiate PR creation, reference specs, and monitor CI until the branch reaches merge readiness.

Can I use this workflow without integrating with wb-pr-craftsman and wb-ci-guardian agents?

No, this workflow requires integration with wb-pr-craftsman and wb-ci-guardian agents to properly create PRs referencing spec artifacts and monitor CI checks.

What limitations exist when automating CI monitoring for pull requests?

Limitations include dependency on the wb-ci-guardian agent for verification and the requirement that spec artifacts at .wannabuild/spec are accessible to properly reference design and requirements.