shiplisted

Have the AI branch, commit, push, and create or update a pull request in the current repository. Use when the user says ship, asks to prepare a branch or commit, or wants help following the repo branch and PR workflow without pushing to main.
karloows/orchraft · ★ 2 · AI & Automation · score 68

Install: claude install-skill karloows/orchraft

# Ship Workflow Use this skill when the user asks the AI to ship work. ## Contents - [At A Glance](#at-a-glance) - [Trigger Rules](#trigger-rules) - [What This Is Not](#what-this-is-not) - [Prerequisites](#prerequisites) - [Default Path](#default-path) - [Naming And Text](#naming-and-text) - [Guardrails](#guardrails) - [Stop Conditions](#stop-conditions) - [Handoff](#handoff) - [Response Examples](#response-examples) ## At A Glance 1. Inspect the current branch, status, and actual diff. 2. Validate the touched area. 3. Use the current non-`main` branch, or create a policy-compliant branch from `main` when currently on `main`. 4. Stage only intended changes, commit with a policy-compliant message, then push. 5. Create or update the pull request and report the branch, commit, PR, and validation result. ## Trigger Rules - Only start this workflow when the user's current message explicitly asks to ship, create a branch/commit/PR, or otherwise gives a clear go signal for the full ship workflow. - Do not infer shipping approval from the fact that changes were just made, validation passed, a prior turn discussed shipping, or the work appears ready. - If the user asks for edits, review, validation, or policy changes without a current-turn ship request, make the changes only and wait for an explicit ship/go confirmation before committing, pushing, or opening/updating a PR. ## What This Is Not - Not a land workflow for merging pull requests or deleting topic