11---
2- name : ship
2+
3+ # # name: ship
34description : Commit, push, and open a PR to staging in one shot
4- ---
55
66# Ship Command
77
@@ -13,21 +13,20 @@ When the user runs `/ship`:
1313
14141. **Check git status** - See what files have changed
15152. **Generate a commit message** following this format : ` type(scope): description`
16- - Types: ` fix ` , ` feat ` , ` improvement ` , ` chore `
17- - Scope: short identifier (e.g., ` undo-redo ` , ` api ` , ` ui ` )
18- - Keep it concise
19-
20- 3 . ** Run lint ** - Run ` bun run lint ` from the repo root to fix formatting issues before staging
21-
16+ - Types : ` fix` , `feat`, `improvement`, `chore`
17+ - Scope : short identifier (e.g., `undo-redo`, `api`, `ui`)
18+ - Keep it concise
19+ 3. **Run pre-ship checks** from the repo root before staging :
20+ - ` bun run lint` to fix formatting issues
21+ - ` bun run check:api-validation:strict ` to catch boundary contract failures before CI
22224. **Stage and commit** the changes with the generated message
23-
24235. **Push to origin** using the current branch name
25-
26246. **Create a PR** to staging with a description in the user's voice
2725
2826# # Commit Message Format
2927
3028Based on the repo's commit history :
29+
3130` ` `
3231fix(scope): description for bug fixes
3332feat(scope): description for new features
@@ -61,6 +60,7 @@ Tested manually (or describe testing)
6160# # PR Creation Command
6261
6362Use this command structure :
63+
6464` ` ` bash
6565gh pr create --base staging --title "COMMIT_MESSAGE" --body "PR_BODY"
6666` ` `
@@ -77,6 +77,7 @@ gh pr create --base staging --title "COMMIT_MESSAGE" --body "PR_BODY"
7777
7878- Short, direct bullet points
7979- No unnecessary explanation
80- - "Tested manually" is acceptable for testing section
80+ - " Tested manually" is acceptable for testing section; include lint and boundary validation results when run
8181- Checkboxes filled in appropriately
8282- No screenshots section unless UI changes
83+
0 commit comments