菜单
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion by presenting structured options for merge, PR, or cleanup
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when starting any conversation — establishes how to find and use Techneering skills, requiring skill invocation before ANY response including clarifying questions
Create distinctive, production-grade frontend interfaces with high design quality. Auto-stacked onto an implementation path when a task involves frontend/UI work — pages, components, layouts, styles, interactions. Also available on demand as tn:craft.
Use after tn:audit passes, when completing major features, or before merging — dispatches a global cross-task code review covering consistency, architecture, and security (distinct from tn:assemble's per-task review)
Use when executing implementation plans with independent tasks in the current session
Verify implementation matches change artifacts — dual-layer verification of code vs spec compliance and code vs real requirements. Use after implementation is complete.
Use when you have a spec or requirements for a multi-step task, before touching code
| name | ship |
| description | Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion by presenting structured options for merge, PR, or cleanup |
Guide completion of development work. Verify tests, present clear options, execute the chosen workflow, clean up.
VERIFY TESTS → PRESENT OPTIONS → EXECUTE CHOICE → CLEAN UP.
No merge without verification. No discard without confirmation.
Before presenting options, verify tests pass:
# Run project's test suite
npm test / cargo test / pytest / go test ./...
If tests fail: Stop. Report failures. Don't proceed. If tests pass: Continue to Step 2.
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
Present exactly these 4 options:
Implementation complete. What would you like to do?
1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
4. Discard this work
Which option?
git checkout <base-branch>
git pull
git merge <feature-branch>
<test command>
git branch -d <feature-branch>
Then: Cleanup worktree
git push -u origin <feature-branch>
gh pr create --title "<title>" --body "<body>"
Then: Cleanup worktree
Report: "Keeping branch . Worktree preserved at ." Don't cleanup worktree.
Confirm first: Require typed "discard" confirmation.
Then: Delete branch + cleanup worktree.
Also: Ask user if they want to remove the change directory from techneering/changes/. If yes, move to techneering/archive/YYYY-MM-DD-<name>-discarded/.
For Options 1, 2, 4:
git worktree list | grep $(git branch --show-current)
# If in worktree:
git worktree remove <worktree-path>
| Thought | Reality |
|---|---|
| "Tests passed before, no need to rerun" | Must rerun before merge — context may have changed |
| "Discard without confirmation" | Discard is irreversible — must have typed confirmation |
| "Force push is fine" | Force push may overwrite others' work unless the user explicitly asks |
| "Skip merge, push directly" | Unmerged branches may have hidden conflicts |
| "Not enough options" | Exactly 4 options — don't add or remove any |
| Excuse | Reality |
|---|---|
| "Tests should pass" | "Should" is not verification — run to confirm |
| "Small changes don't need a PR" | Small changes can still conflict — PR is a safety net |
| "Just force push" | Not allowed unless the user explicitly requests it |
| "Discard without confirmation" | Discard is irreversible — must confirm |
| "Worktree doesn't need cleanup" | Leftover worktrees cause confusion and disk bloat |
| Dimension | Key point |
|---|---|
| Precondition | All tests must pass |
| 4 options | Merge / PR / Keep / Discard |
| Confirmation | Discard requires typed "discard" |
| Worktree cleanup | Options 1/2/4 clean up, option 3 keeps |
| Forbidden | Unconfirmed discard / force push / skipping tests |
When done:
tn:vault to archive the change