菜单
Use when implementation is complete and verified, to integrate the work - merge, PR, or cleanup - after a final evidence check.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | finishing |
| description | Use when implementation is complete and verified, to integrate the work - merge, PR, or cleanup - after a final evidence check. |
Verify once more, detect the workspace, present clear options, execute the choice, clean up.
Announce: "I'm using finishing to complete this work."
Run the project's tests one more time. If anything fails, stop - show the failures and fix before integrating. Do not merge or open a PR on red.
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
GIT_DIR == GIT_COMMON → normal repo, no worktree to clean. Otherwise you are in a worktree; clean it up only if you created it (path under .worktrees/).
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
Or ask: "This branch split from main - correct?"
Implementation complete. What would you like to do?
1. Merge back to <base> locally
2. Push and open a Pull Request
3. Keep the branch as-is
4. Discard this work
Which option?
Keep it to these four - no extra explanation.
Branch history is already clean - one commit per acceptance criterion - so keep those commits by default. Only squash the branch into a single commit if the user asks for it (git merge --squash <branch>, then one commit).
cd to the main repo root, git checkout <base> && git pull && git merge <branch>, re-run tests on the merged result, then (if you own the worktree) remove it and git branch -d <branch>.git push -u origin <branch> and open the PR. Keep the worktree - it is needed for review iteration.discard. Then cd to main root, remove the worktree if you own it, git branch -D <branch>.Merge on failing tests · delete work without typed confirmation · force-push unless asked · remove a worktree you did not create or before the merge succeeded · run git worktree remove from inside the worktree.
Use to build an approved detailed spec task by task in the current session - tests required, single-agent by default, subagents only for large or parallel tasks.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores intent, requirements, and design before implementation.
Use after a design is approved in brainstorming, to turn it into one layered detailed spec (acceptance criteria, tasks, and how to verify) before touching code.
Use when you hit any bug, test failure, or unexpected behavior - find the root cause before proposing a fix.
Use when starting any conversation - establishes how to find and use decentpowers skills and the workflow they form.
Use before claiming work is complete, fixed, or passing - runs the deterministic gate (tests, build, lint, types, acceptance) and one light judgment review, with evidence before any claim.