skills.rest
gyuha
gyuhaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sg-ship

Merge a phase branch into the base branch and push to remote.

2|Updated May 15, 2026
Search Tags:#git#development workflow#pull request#merge#branch deployment#handoff tracking#learning loop orchestration
One-click install
npx skills add https://github.com/gyuha/super-gsd --skill sg-ship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sg-ship
Source: https://github.com/gyuha/super-gsd/tree/main/.agents/skills/sg-ship
Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents the fragile “last mile” of getting a completed phase merged and pushed, which otherwise breaks continuity between planning, implementation, and retrospection.

Core Features & Use Cases

  • Resolves the target phase automatically: Uses a provided phase argument or reads the current Phase from .planning/STATE.md to decide what to ship.
  • Guards the merge with safety checks: Blocks shipping when uncommitted changes exist to avoid overwriting or losing work.
  • Orchestrates delivery with the right path: Delegates to GSD (when available) or guides a manual git merge + push + optional PR creation flow (when GSD is absent); records a ship event in .planning/HANDOFF.md for traceability.

Quick Start

Run sg-ship with no arguments to ship the current phase resolved from .planning/STATE.md.

Frequently Asked Questions about sg-ship

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

FAQPage Schema
How do I merge a phase branch into a base branch and push it without losing uncommitted work?▼

To merge a phase branch safely, the workflow blocks shipping when uncommitted changes exist, then merges the phase branch into the base branch and pushes it to the remote repository. It also records a ship event in .planning/HANDOFF.md for traceability.

What is the best way to finalize phase implementation and hand off completed development work?▼

Finalizing phase work requires merging the completed phase branch into the base branch and pushing to remote. The workflow resolves the target phase automatically from a phase argument or .planning/STATE.md, writes a ship record into .planning/HANDOFF.md, and handles decimal phase numbers.

Do I need a GSD environment to automate git merge and push for branch deployment?▼

You do not need a GSD environment to automate git merge and push. The workflow supports optional GSD delegation to gsd-ship when available, but performs a direct git merge and push flow when GSD is missing.

How does handoff tracking work when shipping completed phase branches?▼

Handoff tracking works by writing a ship record into .planning/HANDOFF.md when a phase branch is merged and pushed. This records the ship event for traceability, bridging the gap between planning, implementation, and retrospection learning loops.

Why does my branch deployment fail when I try to merge with uncommitted changes?▼

Branch deployment fails because the workflow enforces no-uncommitted-changes validation before merging. This safety check blocks shipping to avoid overwriting or losing work, ensuring only clean phase branches are merged into the base branch.

Related Skills

Explore More Software Engineering Skills→
sidunrealdesidunrealde

remove-phase

Remove unstarted future phases from a project roadmap and renumber subsequent phases.

Community
Advanced
pingdiorpingdior
7

ai-native-lean-company

Analyze organizations and draft transformation roadmaps for AI-native lean operations.

Community
Intermediate
mcampbellrmcampbellr

gsd-config

Configure GSD settings for workflow toggles, advanced options, and model profiles.

Community
Intermediate
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate