ship-skills

Shepherd an open PR to merge. Watches CI, fixes failures, addresses review comments, resolves merge conflicts, and enables auto-merge when green. Use after opening a PR, when the user says "babysit", "watch the PR", "get this merged", or as the final step of /ship.

Visual and UX review pass for any change that touched UI — frontend components, HTML, CSS, templates, dashboards, CLI output formatting, or anything a human looks at. Use whenever a diff includes UI files, when the user asks for a design review, or as part of /ship. If the diff touched nothing user-visible, state that and exit immediately.

Commit, push, and open a pull request for the current change. Use when the user says "open a PR", "ship this", "commit and push", or as the PR step of /ship. Handles branch hygiene, commit message quality, and PR description.

Take a finished change from local diff to merged PR. Use whenever the user says "ship it", "/ship", "get this merged", or has a completed change ready to go out. Drives the change to a goal state through non-negotiable quality gates.

Prove a change actually works before it ships. Use whenever a change is "done" and needs validation — after implementing a feature, fixing a bug, or before opening a PR. Also trigger when the user says "verify", "check this works", "is this actually working", or invokes /ship. Tests passing is not sufficient evidence; this skill drives the change end-to-end.