القائمة
Cleans up a git worktree after development is complete. Removes the worktree folder, unregisters it from git, and optionally deletes the local branch. Called by finish-development.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | worktree-finish |
| description | Cleans up a git worktree after development is complete. Removes the worktree folder, unregisters it from git, and optionally deletes the local branch. Called by finish-development. |
| version | 1 |
Properly removes a git worktree after work is done. Always use this instead of rm -rf — git needs to unregister the worktree or the branch stays locked.
Invoked by finish-development when the user confirms a worktree needs cleanup.
project.name → to resolve worktree path
vcs.worktrees.path → base path (default: ~/worktrees/{{project.name}})
git worktree list
Show the list and ask:
"Which worktree do you want to remove?
{list of active worktrees with paths and branches}"
If only one non-main worktree exists, pre-select it and confirm:
"Remove worktree at {path} (branch: {branch})? (y/n)"
"Is the PR for {branch} merged?
A) Yes — remove the worktree
B) Not yet — I'll come back later"
If B: stop. Do not remove the worktree. The developer may need to go back to it for review changes.
git worktree remove {path}
If it fails (uncommitted changes):
git worktree remove --force {path}
Only use --force after confirming with the user that uncommitted changes can be discarded.
Then prune any stale references:
git worktree prune
"Delete the local branch {branch} too?
A) Yes — it's merged, I don't need it
B) No — keep it"
If A:
git branch -d {branch}
If -d fails (not fully merged according to git): warn the user and use -D only with explicit confirmation.
"Worktree removed: {path}
Branch: {kept / deleted}
All clean."
rm -rf the worktree folder — always use git worktree removeFinalizes development work — verifies build, pushes branch, creates PR, transitions ticket to review, and optionally cleans up worktree. Called by orchestrate when the user signals work is done.
Implements tasks from plan.md with TDD, task manager integration, and PR creation. Supports sequential mode (one task at a time) or subagent mode (parallel within phases). Reads commit format and platform config from kitt.json.
Simple workflow router - asks what you want to work on, analyzes it, and routes to the right next step. Handles epic → US workflow and flat feature workflow. Auto-syncs metadata on US completion.
Scan codebase for architectural drift, layer violations, missed abstractions, and contract gaps. Produces structured proposals with context, problem, and expected fix. Integrates with task manager and implement pipeline.
Validates refined feature against project architecture. Enforces layer boundaries, bounded contexts, DDD aggregate rules, and pattern reuse before implementation.
Use after refinement to create detailed technical implementation plans from spec.md - breaks down user stories into tasks, dependencies, technical decisions, and optional task manager tickets