skilld
All skills
garrytan avatar

/ship

@96764e8 official
by Garry Tangarrytan/gstack135k stars
20,051

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack)

Requires /gstack-upgrade /plan-tune /retro /qa-only /document-generate /context-save /learn /qa /review /browse /autoplan /plan-eng-review /design-review /document-release

Ask your Agent

Use this Skill: https://skilld.dev/gh/garrytan/gstack/ship

This session only. Nothing lands on disk.

sectionschangelog.md

≈477 tokens on demand. Your agent reads this file only when SKILL.md points to it.

<!-- AUTO-GENERATED from changelog.md.tmpl — do not edit directly --> <!-- Regenerate: bun run gen:skill-docs -->

Step 13: CHANGELOG (auto-generate)

  1. Read CHANGELOG.md header to know the format.

  2. First, enumerate every commit on the branch:

    git log origin/<base>..HEAD --oneline

    Copy the full list. Count the commits. You will use this as a checklist.

  3. Read the full diff to understand what each commit actually changed:

    git diff origin/<base>

  4. Group commits by theme before writing anything. Common themes:

    • New features / capabilities
    • Performance improvements
    • Bug fixes
    • Dead code removal / cleanup
    • Infrastructure / tooling / tests
    • Refactoring

  5. Write the CHANGELOG entry covering ALL groups:

    • If existing CHANGELOG entries on the branch already cover some commits, replace them with one unified entry for the new version
    • Categorize changes into applicable sections:
      • ### Added — new features
      • ### Changed — changes to existing functionality
      • ### Fixed — bug fixes
      • ### Removed — removed features
    • Write concise, descriptive bullet points
    • Insert after the observed file header, before the first release entry, dated today
    • Format: ## [X.Y.Z.W] - YYYY-MM-DD
    • Voice: Lead with what the user can now do that they couldn't before. Use plain language, not implementation details. Never mention TODOS.md, internal tracking, or contributor-facing details.

  6. Cross-check: Compare your CHANGELOG entry against the commit list from step 2. Every commit must map to at least one bullet point. If any commit is unrepresented, add it now. If the branch has N commits spanning K themes, the CHANGELOG must reflect all K themes.

Do NOT ask the user to describe changes. Infer from the diff and commit history.

Source: SKILL.md on GitHub

Third-party checks

1 alert3d4 checks · Risk SAFE
  • Gen Agent Trust Hub3d

    The 'ship' skill is a highly sophisticated automation workflow for shipping code, including merging, testing, and PR creation. It features robust security mitigations like redaction scans and trust boundaries for subagents. The primary security considerations involve its inherent attack surface for indirect prompt injection—processing untrusted data like PR bodies and plan files—and the use of dynamic execution to generate and run tests at runtime. These are core functionalities for the skill's purpose and are accompanied by safety gates.

  • Socket3d

    No alerts

  • Snyk3d

    Risk: LOW · No issues

  • Runlayer6mo

    1/1 file flagged

Provenance

Signed by skilld at 96764e8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 15 hours ago.

Activeupdated 2 days ago

Capability

What it can do
Runs commands Reads files Edits files Network
preamble-tier
4
version
1.0.0
triggers
[
  "ship it",
  "create a pr",
  "push to main",
  "deploy this"
]
All 9 allowed tools
BashReadWriteEditGrepGlobAgentAskUserQuestionWebSearch

Topics

README badge

README badge for garrytan/gstack/ship

What it does

Orchestrates a complete release workflow: detects the base branch, merges it, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates a pull request. Built on the gstack tool and triggered by phrases like "ship it" or "create a PR".

Generated from the current SKILL.md.

Frequently asked

What does this skill do?
The ship skill automates the full release workflow: detect and merge the base branch, run tests, review the diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Invoke it when code is ready to ship.
When should I invoke this skill instead of pushing manually?
Invoke ship proactively whenever the user says code is ready, asks to deploy, wants to push code up, or requests creating a PR. Do not push or create a PR directly — the skill handles the entire workflow.
What tools and permissions does this skill use?
The skill uses Bash, Read, Write, Edit, Grep, Glob, Agent, AskUserQuestion, and WebSearch. It requires git access and permission to commit, push, and create pull requests.
Does this skill work in plan mode?
Yes. In plan mode, treat the skill file as executable instructions and follow it step-by-step. The first AskUserQuestion call satisfies plan mode's end-of-turn requirement. Do not call ExitPlanMode until the workflow completes.

Generated from the current SKILL.md. These answers refresh after source changes.