sw-ship

Create a pull request with evidence-mapped body after verifying gates.

9|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sw-ship
Source: https://github.com/Obsidian-Owl/specwright/tree/main/skills/sw-ship
Command: npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of shipping completed work units by creating verified pull requests, ensuring all acceptance criteria are met and evidence is mapped.

Core Features & Use Cases

  • Automated PR Creation: Generates pull requests with bodies that map acceptance criteria to evidence.
  • Gate Verification: Ensures all required gates have passed before shipping.
  • Workflow State Management: Updates the workflow status to 'shipped' upon successful PR creation.
  • Use Case: After completing a feature and passing all verification gates, use this skill to automatically create a PR for review, complete with a summary of changes and links to supporting evidence.

Quick Start

Use the sw-ship skill to create a pull request for the current work unit.

Frequently Asked Questions about sw-ship

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

FAQPage Schema
How do I automatically create a pull request with mapped acceptance criteria evidence?

To automatically create a pull request with mapped acceptance criteria evidence, you can use a shipping workflow that verifies all gates have passed and generates a PR body linking to the supporting evidence. This ensures all criteria are met before review.

What is the best way to verify CI/CD gates before pushing a git branch?

The best way to verify CI/CD gates before pushing a git branch is to run pre-flight checks within defined stage boundaries. This gate verification ensures all required CI/CD checks have successfully passed before proceeding to create a pull request.

How does automated workflow state management work after shipping a pull request?

Automated workflow state management updates the workflow status to 'shipped' upon successful pull request creation. It manages workflow state updates and cleans up feature branches post-merge, ensuring the git workflow remains tidy and accurate.

Can I use git protocols to manage feature branch cleanup and PR creation?

Yes, you can use git protocols to manage feature branch cleanup and PR creation. This approach operates within defined stage boundaries and pre-flight checks, utilizing git protocols for branch, push, and pull request operations to ship verified work units.

What happens if verification gates fail during the pull request creation process?

If verification gates fail during the pull request creation process, the shipping workflow halts. Gate verification ensures all required gates have passed before shipping, preventing the creation of a pull request until all acceptance criteria are successfully met.

Do I need to manually map evidence to a pull request body when shipping code?

No, you do not need to manually map evidence to a pull request body when shipping code. Automated PR creation generates pull requests with bodies that map acceptance criteria to evidence, streamlining the workflow and ensuring verified evidence is attached.