branch-finishlisted

# Branch Finish Checklist Skill Before merging or closing a branch, verify the work is actually done and the branch is clean. This prevents partial merges and repo pollution. ## When to use this skill - About to run `git merge`, `git push`, or close a worktree - User says "merge this", "I'm done", "wrap it up" - Task is marked complete in TODO.md ## The Checklist Run each step and show output. Do not skip. ### 1 — Tests pass ```bash bash core/tests/hooks/run-hook-tests.sh 2>&1 | tail -5 ``` Required: `0 failed`. If tests fail → stop. Do not merge. ### 2 — No rogue files ```bash git status --short ``` Check for: - Untracked files that should not exist (`.env*`, `*.log`, `node_modules/`) - Modified files outside the task scope If anything unexpected appears → investigate before merging. ### 3 — Diff is clean ```bash git diff main...HEAD --stat ``` Show the list of changed files. Confirm with user: "These N files will be merged. Correct?" ### 4 — No debug artifacts ```bash git diff main...HEAD | grep -n "console\.log\|debugger\|TODO REMOVE\|HACK\|XXX" || echo "none found" ``` If anything found: list it. User decides whether to clean up. ### 5 — Commit messages are conventional ```bash git log main..HEAD --oneline ``` Each commit message should follow `type: subject` (feat, fix, chore, docs, refactor). If not: warn but do not block. ### 6 — Present options After checklist passes: ``` Branch finish checklist: PASS What next? 1. Merge locally (git merge int