feature-ship

Automate feature shipping from worktree validation to pull request creation.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/oletizi/writingcontrol.org --skill feature-ship-oletizi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-ship
Source: https://github.com/oletizi/writingcontrol.org/tree/main/.claude/skills/feature-ship
Command: npx skills add https://github.com/oletizi/writingcontrol.org --skill feature-ship-oletizi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes the end-to-end feature delivery workflow, ensuring acceptance criteria are verified, tests are run, and a PR is created for review and merging.

Core Features & Use Cases

  • Verification of acceptance criteria: Validate the workplan and ensure all criteria are marked complete before proceeding.
  • Automated testing workflow: Run unit, integration, and end-to-end tests as part of the ship process.
  • PR preparation & publishing: Create and summarize a pull request, push the feature branch, and update documentation with the PR URL.

Quick Start

Identify the feature in your worktree, verify acceptance criteria, run tests, push the branch, and create a PR.

Frequently Asked Questions about feature-ship

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

FAQPage Schema
How do I automate the git feature branch workflow before creating a pull request?

To automate the git feature branch workflow, this skill reads a workplan, verifies acceptance criteria, runs tests, pushes the branch, and generates a pull request summary.

What is the best way to ensure code review criteria are met before opening a PR?

Ensuring code review criteria are met involves validating the workplan and confirming all acceptance criteria are marked complete before proceeding to push the branch and create the PR.

Can I automatically run tests and push a feature branch at the same time?

Yes, you can run tests and push a feature branch concurrently as part of an automated end-to-end ship workflow that executes unit, integration, and end-to-end tests before publishing.

How do I create a pull request with an automated summary from a git branch?

Creating a pull request with an automated summary requires pushing the completed feature branch after tests pass, which then produces a PR with a generated summary and updates documentation with the URL.

Do I need a workplan to use an automated feature shipping process?

Yes, a workplan is required because the feature shipping process reads it to verify that all defined acceptance criteria are successfully met before running tests and creating a pull request.

What happens if acceptance criteria are not verified during the feature ship workflow?

If acceptance criteria are not verified, the feature ship workflow halts because the process requires all workplan criteria to be marked complete before running tests and pushing the feature branch.