ship

Merge feature branches into master with backlog archiving and reflection invocation.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/misty-step/scry --skill ship-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/misty-step/scry/tree/main/.agent/skills/ship
Command: npx skills add https://github.com/misty-step/scry --skill ship-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It simplifies the final step in the development workflow by automating branch merging, backlog archiving, and reflection integration.

Core Features & Use Cases

  • Final Mile Deployment: Land pre-approved backlog branches into master with minimal manual steps.
  • Backlog Management: Archive completed backlog files into an organized directory structure to maintain clear project history.
  • Use Case: When ready to merge a feature branch, this skill automates the process of merging, archiving backlog tickets, updating related docs, and invoking reflection to capture lessons learned.

Quick Start

Use the ship skill to close off the current development branch, archive backlog tickets, and prepare for release.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate merging a feature branch into master while archiving the backlog?

Automating branch merging and backlog archiving streamlines final deployment by landing pre-approved branches into master while moving completed backlog tickets into an organized directory structure.

What is the best way to capture lessons learned during a code merge?

Capturing lessons learned during a merge is handled by invoking reflection integration, which automatically documents retrospective insights to ensure consistent project closure and knowledge capture.

How do I enforce quality gates before finalizing a branch deployment?

Enforcing quality gates before finalizing a branch deployment requires strict adherence to backlog closure policies, ensuring all pre-approved backlog branches meet project standards before merging into master.

How does backlog archiving work when closing off a development branch?

Backlog archiving works by moving completed backlog files into an organized directory structure, maintaining clear project history while preparing the current development branch for release.

Can I use this workflow for managing backlog tickets across multiple feature branches?

Managing backlog tickets across multiple feature branches is supported through meticulous backlog management, archiving completed items per branch to maintain clear project history and closure.