plugins/pokayokay/skills/finishing-branch/SKILL.md
Use after a task, story, epic, worktree, or development branch is implementation-complete and freshly verified. Presents merge, PR, keep, or discard choices and records evidence before cleanup.
npx skillsauth add srstomp/pokayokay finishing-branchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Close a development branch deliberately. Do not merge, delete, or mark work complete until the branch has fresh verification evidence and a clear user or workflow decision.
git status --short --branch.git diff --stat and targeted file diffs.| Choice | When to use | Action | |--------|-------------|--------| | Merge | Local integration is desired now | Merge into the base branch after verification | | Pull request | Human review or CI is needed | Push branch and open a PR with verification notes | | Keep | More work remains or user wants a checkpoint | Leave branch/worktree intact and record next steps | | Discard | Work is abandoned or superseded | Confirm explicitly, then remove branch/worktree |
## Branch Finish
**Branch**: [name]
**Base**: [branch]
**Verification**: `command` -> PASS/FAIL
**Changed Files**: [summary]
**Recommended Path**: PR / merge / keep / discard
**Reason**: [short rationale]
Destructive cleanup, branch deletion, and discarding changes require explicit human confirmation unless the user already requested that exact action.
development
Git worktree management for isolated task development
development
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
testing
Use before claiming work is done, fixed, passing, ready to commit, ready to PR, or ready to mark complete. Requires fresh verification evidence and explicit command output before success claims.
development
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.