plugins/pokayokay/skills/worktrees/SKILL.md
Git worktree management for isolated task development
npx skillsauth add srstomp/pokayokay worktreesInstall 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.
Guide for managing git worktrees in pokayokay.
| Task Type | Default | Override | |-----------|---------|----------| | feature | Worktree | --in-place | | bug | Worktree | --in-place | | spike | Worktree | --in-place | | chore | In-place | --worktree | | docs | In-place | --worktree | | test | Inherits | explicit flag |
finishing-branch to choose merge, PR, keep, or discard with verification evidence.worktrees/ (auto-ignored by git)finishing-branch to verify and choose merge, PR, keep, or discardgit worktree list if issues arise| Reference | Description | |-----------|-------------| | worktree-management.md | Lifecycle, completion options, dependency install, troubleshooting | | cleanup-strategies.md | Cleanup criteria, detection, disk management, scheduled cleanup | | parallel-worktrees.md | Parallel execution worktree isolation, conflict prevention |
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.
development
Use when diagnosing bugs, failing tests, build failures, unexpected behavior, flaky tests, regressions, or production incidents. Requires reproduction, root cause evidence, one-hypothesis fixes, and regression verification before editing.