Finishing Grove Workspace
- 9 installs
- 20 repo stars
- Updated February 25, 2026
- chrisbanes/grove
Resolve or clean up a completed Grove workspace by verifying tests pass and presenting merge or cleanup options.
About
Detects a Grove workspace, runs the auto-detected test command, and presents completion options once tests pass. Used when a developer finishes implementation inside a Grove workspace and needs to wrap it up.
- Auto-detects and runs the project test command
- Reads .grove/workspace.json for merge/cleanup
Finishing Grove Workspace by the numbers
- 9 all-time installs (skills.sh)
- Ranked #438 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/chrisbanes/grove --skill finishing-grove-workspaceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 9 |
|---|---|
| repo stars | ★ 20 |
| Last updated | February 25, 2026 |
| Repository | chrisbanes/grove ↗ |
What it does
Resolve or clean up a completed Grove workspace by verifying tests pass and presenting merge or cleanup options.
Files
I'm using the finishing-grove-workspace skill to wrap up this Grove workspace.
Workflow
Step 1: Detect workspace
test -f "$(git rev-parse --show-toplevel)/.grove/workspace.json"If .grove/workspace.json is not found: this is not a Grove workspace. Use superpowers:finishing-a-development-branch instead.
Step 2: Verify tests pass
Auto-detect the test command from marker files:
| Marker file | Test command |
|---|---|
go.mod | go test ./... |
package.json | npm test |
Cargo.toml | cargo test |
build.gradle / build.gradle.kts | ./gradlew test |
pyproject.toml / requirements.txt | pytest |
Makefile | make test |
If tests fail, stop. Do not present completion options.
Step 3: Read workspace metadata
cat .grove/workspace.jsonExtract id, golden_copy, and branch from the JSON output.
Step 4: Present options
Present exactly these four options:
1. Push branch and create a Pull Request 2. Push branch and destroy workspace 3. Keep workspace as-is 4. Discard work and destroy workspace
Step 5: Execute choice
Option 1: Push + PR
Derive the PR title from the branch name and the body from a summary of commits since the golden copy.
git push -u origin <branch>
gh pr create --title "<title>" --body "<body>"
grove destroy <workspace-id>
cd <golden-copy-path>Option 2: Push + destroy
git push -u origin <branch>
grove destroy <workspace-id>
cd <golden-copy-path>Option 3: Keep as-is
Report: "Keeping workspace at <path>."
Option 4: Discard
Require the user to type "discard" before proceeding.
grove destroy <workspace-id>
cd <golden-copy-path>Quick Reference
| Option | Push branch | Create PR | Keep workspace | Cleanup |
|---|---|---|---|---|
| 1. Push + PR | yes | yes | no | yes |
| 2. Push + destroy | yes | no | no | yes |
| 3. Keep as-is | no | no | yes | no |
| 4. Discard | no | no | no | yes |
Common Mistakes
- Skipping test verification — never present completion options before confirming tests pass.
- Open-ended questions — always present the structured four-option list; do not ask "what would you like to do?" in free form.
- Automatic workspace cleanup — if the user selects option 3, do not run
grove destroy. Respect the choice to keep the workspace. - No confirmation for discard — option 4 destroys uncommitted work; always require the user to type "discard" before executing.
Red Flags
.grove/workspace.jsonmissing but.grove/config.jsonpresent — the agent is on the golden copy, not in a workspace. Route tosuperpowers:finishing-a-development-branch.grove destroyfails — the workspace ID may be stale. Rungrove listto confirm the workspace exists before retrying.
Integration
- Replaces:
superpowers:finishing-a-development-branchwhen in a Grove workspace - Called by:
superpowers:subagent-driven-development(Step 7),superpowers:executing-plans(Step 5) - Pairs with:
grove:using-grove
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148