ship

Verify gates, route task tails to cog memory, and present shipping options.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bketelsen/ytsejam --skill ship-bketelsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/bketelsen/ytsejam/tree/main/contrib/skills/ship
Command: npx skills add https://github.com/bketelsen/ytsejam --skill ship-bketelsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing development work reliably requires gating, task-tail routing, and consistent post-release hygiene. This Skill orchestrates gate verification, routes per-task tails to cog memory, presents merge/PR/keep/discard options, cleans up the worktree, and updates CHANGELOG plus the cog wiki/dev-log.

Core Features & Use Cases

  • Gate verification and per-task tail routing to memory for project review.
  • Presenting shipping options (Merge, PR, Keep, Discard) and performing cleanup and changelog/wiki updates.
  • Supports end-to-end shipping workflows, including re-verification of gates after changes and proper record-keeping across dev-log and cog-wiki.

Quick Start

Trigger ship after a feature is ready to verify the gate, choose an option, and record changes.

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 creation after passing branch quality gates?

To automate pull request creation after passing branch quality gates, you can trigger a workflow that verifies gate checks, routes task details to memory, and presents shipping options including merge, PR, keep, or discard. This ensures branch-based work is verified before finalizing.

What is gate verification in a git workflow?

Gate verification in a git workflow is a checkpoint process that runs quality checks on a branch before allowing finalization. It ensures development work meets standards, supports re-verification after changes, and routes per-task tails to memory for documented decision tracking.

How do I update changelog and dev-log after merging a branch?

To update changelog and dev-log after merging a branch, use an end-to-end shipping orchestration workflow that performs worktree cleanup, records documented decisions, and automatically updates the changelog and cog wiki following your chosen merge or discard path.

Can I re-verify quality gates after making changes to a pull request?

Yes, you can re-verify quality gates after making changes to a pull request. The workflow automation applies guardrails for gate re-verification, ensuring that any modifications trigger the checks again before allowing you to proceed with merge or PR options.

Does branch-based workflow automation support worktree cleanup and decision tracking?

Yes, branch-based workflow automation supports worktree cleanup and decision tracking. It orchestrates gate verification, routes per-task tails to cog memory, presents shipping options, and ensures proper record-keeping across dev-log and cog-wiki for documented decisions.