skills.rest
tkersey
tkerseyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ship

Confirm validation signals, summarize proof, and open a non-merged PR via gh.

66|2|Updated Feb 18, 2015
Search Tags:#git#github#validation#beads#ship#pull-request#proof
One-click install
npx skills add https://github.com/tkersey/dotfiles --skill ship-tkersey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/tkersey/dotfiles/tree/main/codex/skills/ship
Command: npx skills add https://github.com/tkersey/dotfiles --skill ship-tkersey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the finalization phase after a validated change by ensuring a reliable proof trail, documenting outcomes, and opening a non-merge PR for review. It prevents shipping without a signal and provides a structured summary that can be shared in PR descriptions and bead comments.

Core Features & Use Cases

  • Confirm a recent validation signal exists; if missing, trigger validation.
  • Summarize proof: collect signals, commands, and outcomes into a concise report.
  • Bead-aware commenting: attach proof to the active bead when beads are used (.beads directory exists).
  • Open a PR (no merge) using gh where applicable, and report status or blockers for follow-up.
  • Guardrails: block shipping without a valid signal and clearly report blockers.

Quick Start

Initiate ship after validation to generate a proof trail and open a non-merge PR.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I open a pull request with proof after validating changes?▼

To open a pull request with proof, the ship Skill confirms a recent validation signal, summarizes the outcomes into a proof trail, and uses gh to prepare a non-merged PR for review.

What is the best way to prevent shipping code without a validation signal?▼

The best way to prevent shipping without a validation signal is using built-in guardrails that block finalization, clearly reporting blockers until a valid proof trail is confirmed.

How do I summarize proof and attach it to my beads workflow?▼

To summarize proof in a beads workflow, the Skill collects signals and outcomes into a concise report, attaching the proof commentary to the active bead when a .beads directory exists.

Can I use the ship Skill to automatically merge my GitHub pull requests?▼

No, you cannot use the ship Skill to automatically merge pull requests. It exclusively prepares a non-merge PR using gh to ensure validated work remains open for manual review.

What happens if I try to finalize work without a recent validation signal?▼

If you try to finalize work without a recent validation signal, the Skill enforces guardrails to block shipping and will attempt to trigger validation before proceeding.

Does the ship pull request workflow require the GitHub CLI?▼

Yes, the ship pull request workflow uses the GitHub CLI (gh) for PR creation where applicable, reporting the status or blockers for follow-up during the finalization phase.

Related Skills

Explore More Software Engineering Skills→
tkerseytkersey
66

beads

Record plan, progress, decisions, and verification in a per-step ledger.

Community
Advanced
apacheapache
79

magpie-pr-management-quick-merge

Identify and rank trivial GitHub pull requests for fast manual review.

Official
Advanced
StonelukasStonelukas

git

Automate Git staging, committing, pushing, PR creation, and merges.

Community
Advanced
skuridinskuridin

pr-create

Generate standardized GitHub pull request titles and descriptions from commit history.

Community
Intermediate