skills/finishing-a-workspace/SKILL.md
Use when implementation is complete and you need to handle workspace completion - merge, PR, keep, or discard
npx skillsauth add BubbleBuffer/superpawers finishing-a-workspaceInstall 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 completion of development work by presenting clear options and handling chosen workflow.
Core principle: Present options → Execute choice → Clean up.
Announce at start: "I'm using the finishing-a-workspace skill to complete this work."
# Try common base branches
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
Or ask: "This workspace split from main - is that correct?"
Present exactly these 4 options, each with one line of guidance:
Implementation complete and verified. What would you like to do?
1. Merge back to <base-branch> locally — solo or local workflows; the workspace plugin handles the merge
2. Push and create a Pull Request — default for shared repos or when review/CI is required
3. Keep the workspace as-is — pause work; resume later without merging or discarding
4. Discard this work — only if the user has explicitly abandoned the workspace
Which option?
One line per option is allowed. Do not add longer explanations or recommendations — the user decides.
Call workspace_remove with merge=true:
workspace_remove(id="<workspace-id>", merge=true)
The plugin switches to the base branch, merges the feature branch, and removes the worktree.
# Push branch
git push -u origin <feature-branch>
# Create PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<2-3 bullets of what changed>
## Test Plan
- [ ] <verification steps>
EOF
)"
Report: "Keeping workspace <name>."
Confirm first:
This will permanently delete:
- Workspace <name>
- All commits: <commit-list>
Type 'discard' to confirm.
Wait for exact confirmation.
If confirmed:
workspace_remove(id="<workspace-id>")
| Option | Merge | Push | Keep Workspace | Cleanup Workspace | |--------|-------|------|----------------|-------------------| | 1. Merge locally | ✓ | - | - | ✓ | | 2. Create PR | - | ✓ | ✓ | - | | 3. Keep as-is | - | - | ✓ | - | | 4. Discard | - | - | - | ✓ (no merge) |
Open-ended questions
No confirmation for discard
Stale workspace recovery
workspace_clean to remove stale workspaces before retryingNever:
Always:
Use after:
subagent-driven-development — all tasks complete, final reviewer and verifier have passed.verification-before-completion — completion claims must be backed by fresh verification evidence before this skill runs.Pairs with:
using-workspaces — created the workspace this skill completes.data-ai
Use when a request involves multiple steps or files, or when an approved design must be turned into a detailed implementation plan
development
Use when deciding which SuperPawers skill should govern a new task or workflow step, before taking any other action
development
Use when starting feature work that needs git isolation or before writing committed spec, plan, or code artifacts
development
Use when a task list exists or is being created for multi-step implementation work, whether from a formal plan or an ad-hoc breakdown