ship-simple-change
Installation
SKILL.md
Ship Simple Change
Automate the full flow: stage specified files → lint → test → commit → push → create PR. Collect all required information up front, then run without further prompts.
When to Use
- User says "push this and create a PR", "ship this change", "commit, push, and open a PR uninterrupted"
- User wants to use the same flow as prepare-commit + create-pr but in one shot with no confirmations
Phase 1: Collect Information Up Front
Before running any git or npm commands, gather (or infer) the following. If anything critical is missing, ask once in a single message:
| Input | Required | Notes |
|---|---|---|
| Files to include | Yes | Explicit paths (e.g. maestro/utils/expoMenu.yml) or "all staged" / "current changes". Do not stage unrelated files. |
| Ticket | Yes | Jira key (e.g. RETIRE-1234) or unticketed → use RETIRE-1908 (placeholder for unticketed work). |
| Branch name | No | Default: [TICKET]-[kebab-case-summary] from change summary (e.g. RETIRE-1908-expo-menu-any-port). |
| Commit message | No | Default: conventional commit generated from staged diff (type: short description). |