ship-a-feature

Automate approved repository changes from request to terminal PR outcome.

229|5|Updated May 25, 2026
One-click install
npx skills add https://github.com/compartmentdev/compartment --skill ship-a-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-a-feature
Source: https://github.com/compartmentdev/compartment/tree/main/.codex/skills/ship-a-feature
Command: npx skills add https://github.com/compartmentdev/compartment --skill ship-a-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end delivery of an approved repository change from request to terminal PR outcome.

Core Features & Use Cases

  • End-to-end feature delivery: coordinates preflight, implementation, review, smoke tests, commits, and PR monitoring.
  • PR orchestration: manages branch creation, CI triggers, and blockers until final PR state.
  • Guardrails: ensures alignment with approved requests and avoids duplication of skills.

Quick Start

Initiate the end-to-end feature shipping workflow from an approved change request to terminal PR outcome.

Frequently Asked Questions about ship-a-feature

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

FAQPage Schema
How do I automate end-to-end feature delivery from code changes to pull requests?

End-to-end feature delivery automation coordinates preflight, implementation, testing, and PR monitoring from an approved change request to a terminal PR state. The workflow manages feature branch creation, runs smoke tests, handles commits, and reports blockers until final resolution.

What is the best way to orchestrate CI/CD workflows and feature branch tracking?

CI/CD workflow orchestration manages branch creation, triggers CI pipelines, and tracks blockers until a terminal PR outcome is reached. It coordinates designated subagents to handle implementation, testing, and code review while enforcing alignment with approved repository changes.

Can I use automated pull request monitoring to track blockers during code review?

Automated pull request monitoring tracks blockers during code review by continuously evaluating PR state until a terminal outcome is reached. It coordinates subagents for smoke tests and commits while enforcing guardrails against duplicating skills or deviating from approved changes.

Does feature branch orchestration handle preflight checks and smoke tests before committing?

Feature branch orchestration handles preflight checks and smoke tests before committing by coordinating designated subagents across the delivery workflow. It enforces guardrails to ensure implementation aligns with approved requests while tracking the dedicated branch to a terminal PR state.

When do I need workflow orchestration for managing repository changes and PR states?

Workflow orchestration for managing repository changes is needed when an approved change must pass preflight, implementation, testing, review, and PR monitoring. It creates a dedicated feature branch, coordinates subagents, and reports terminal PR states or blockers.

Why does automated feature delivery prevent duplication of skills during implementation?

Automated feature delivery prevents duplication of skills during implementation by enforcing guardrails that ensure alignment with approved requests. It coordinates designated subagents across preflight, testing, and review stages while tracking the feature branch to a terminal PR outcome.