菜单
Bundles all uncommitted work from multiple Cursor agent threads on the same branch and checkout into one finish commit, then pushes. Use when the user runs /bundle-ship, /finish-all, or asks to finish and push everything across threads on one checkout.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | bundle-ship |
| description | Bundles all uncommitted work from multiple Cursor agent threads on the same branch and checkout into one finish commit, then pushes. Use when the user runs /bundle-ship, /finish-all, or asks to finish and push everything across threads on one checkout. |
Land all uncommitted changes on the current branch and checkout when multiple agent threads may have contributed — one bundled commit, then push.
SSOT for commit mechanics: .agents/skills/finish/SKILL.md (bundle mode).
SSOT for push mechanics: .agents/skills/push/SKILL.md.
Use bundle-ship | Use plain finish → push instead |
|---|---|
| Multiple agent chats touched the same working folder | Single thread owns the full diff |
| User wants one commit for the whole tree snapshot | User wants thread-scoped commit only |
User explicitly invokes /bundle-ship or /finish-all | Normal session wrap-up |
Skip gate: Clean tree with nothing to commit → report and stop (do not invent work).
Orchestration and bundle intent only. It does not duplicate version rules, staging gates, changelog format, or push safety checks — those stay in finish and push.
If git status or the full diff changes between two fresh reads without this thread editing those paths, stop. Tell the user the tree is still moving; wait until other threads are idle, then re-run.
Copy and track:
Bundle-ship progress:
- [ ] Step 1: Snapshot the full tree
- [ ] Step 2: Confirm bundle scope with user
- [ ] Step 3: Run finish (bundle mode)
- [ ] Step 4: Run push
git status -sb and read the full diff from disk (git diff and git diff --cached; include untracked paths that belong in the release).Tell the user:
finish semver rules.Ask once: ready to bundle-finish and push this snapshot?
If the user declines, stop. If they want thread-scoped finish instead, route to plain finish (no push in that turn unless they ask).
Task backlog: If src/config/app-tasks.json has multiple in-progress rows from different threads, ask which task(s) to archive before commit — same as finish, but expect ambiguity more often in multi-thread landings.
Read .agents/skills/finish/SKILL.md and execute it with these overrides:
finish default | bundle-ship override |
|---|---|
| Concurrent smoke → AskQuestion (pause / bundle / stash / wait) | Skip the four-option menu — user already chose bundle by invoking this skill |
| Scope = this thread’s work | Scope = full tree from Step 1 |
| Ends with offer to push | Continue to Step 4 in this same turn after a successful commit |
| Stash lane / wait-and-recheck | Out of scope — user must pause other threads first |
Follow all other finish requirements: archive task when applicable, version/changelog gate, staging decision gate, ready-to-commit confirmation, commit message standards, protected files, feature-doc validation.
One commit for the full snapshot. Changelog and version bump (when required) must reflect all bundled changes.
After a successful commit:
.agents/skills/push/SKILL.md and execute it in this same turn.push and report — do not commit-fix inside push.| Will NOT do | Mark |
|---|---|
| Per-thread separate commits | excluded |
| Coordinate git worktrees or merge branches first | excluded |
| Stash other threads’ work and restore after push | excluded — use plain finish Option 3 if needed |
| Auto-poll or wait for other threads | excluded — user pauses them |
Replace finish or push rules | excluded — delegates SSOT |
| Open PRs or promote to production | deferred — after push, user opens PR per workflow rules |
Not bundle-ship | Use instead |
|---|---|
| Single-thread wrap-up | finish → push |
| Only push existing commits | push |
| Validate before landing | validate |
| Concurrent smoke; user unsure about bundle | finish (full AskQuestion menu) |
Treat these as the same skill: /bundle-ship, /finish-all, “finish and push everything across threads.”
Interview the user until scope edges and interaction boundaries are aligned and the decision tree is resolved. Focuses on where the feature stops, what it will NOT do or touch, and how it meets other functionality. Chat-only alignment — authors no artifact. Use to stress-test scope/boundaries before feature or plan, or when the user says "grill me".
Picks the next action and skill, then invokes it (read that SKILL.md and execute the workflow in the same turn). Mid-thread: continue the logical next step on active work. Idle or new: fall back to gates and app-tasks.json backlog. Maps situations to project, user, and plugin skills; resolves overlaps. Product context SSOT: documentation/DOC_APP_VISION.md. Use when the user types /router, asks which skill to use, starts ambiguous work, or routes slash commands to SKILL.md files. Bare /router is next-action dispatch (not finish).
Challenges and simplifies a concrete feature to reduce steps, clicks, and cognitive load (flow and code modes by default). Use when the user targets a workflow and asks whether it is overbuilt, or runs /challenge.
Systematically audit the codebase for consolidation, abstraction, and redundancy removal opportunities across features. Use when the user asks to find duplication, consolidate code, audit for redundancy, reduce repetition, or identify shared patterns that should be unified.
Structured scientific debugging for runtime bugs, regressions, flaky behavior, frontend/backend failures, Supabase/RLS/Auth/Storage issues, and user-reported errors. Use when the user invokes /debug, asks to debug, reports an error, or describes inconsistent behavior.
Runs systematic new-feature engineering with mandatory decision stops; produces product/requirements artifacts, not DEVELOPMENT_PLAN.md (plan is SSOT for execution plans). Use for new feature requests before planning. Not implement, validate, or finish.