ship

SKILL.md

Ship

Overview

Finalize deliverables after validation and produce a concise proof trail.

Workflow

  1. Confirm a recent validation signal exists for the current change set; if not, run validate.
  2. Summarize proof: commands/signals and outcomes.
  3. Capture the proof directly in the PR description (or update the PR body if it already exists).
  4. Open a PR (do not merge), using gh where applicable.
  5. Report PR status and any remaining follow-ups.

Guardrails

  • Never ship without a signal.
  • Keep proof concise and scoped to this change.
  • If PR creation is blocked (auth/remote), state the exact blocker and next command.

Output

  • Proof summary (signals + results).
  • PR creation status.
  • Next steps if any.
Weekly Installs
17
GitHub Stars
43
First Seen
14 days ago
Installed on
gemini-cli17
opencode17
codebuddy17
github-copilot17
codex17
kimi-cli17