// Use when implementation is complete, all tests pass, and the agent is operating inside a Grove workspace that needs to be resolved or cleaned up
| name | finishing-grove-workspace |
| description | Use when implementation is complete, all tests pass, and the agent is operating inside a Grove workspace that needs to be resolved or cleaned up |
I'm using the finishing-grove-workspace skill to wrap up this Grove 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.
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.
cat .grove/workspace.json
Extract id, golden_copy, and branch from the JSON output.
Present exactly these four options:
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 ."
Option 4: Discard
Require the user to type "discard" before proceeding.
grove destroy <workspace-id>
cd <golden-copy-path>
| 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 |
grove destroy. Respect the choice to keep the workspace..grove/workspace.json missing but .grove/config.json present — the agent is on the golden copy, not in a workspace. Route to superpowers:finishing-a-development-branch.grove destroy fails — the workspace ID may be stale. Run grove list to confirm the workspace exists before retrying.superpowers:finishing-a-development-branch when in a Grove workspacesuperpowers:subagent-driven-development (Step 7), superpowers:executing-plans (Step 5)grove:using-groveUse when configuring Grove for a repository that does not yet have a `.grove/config.json`, or when a user asks to configure Grove in their project
Use when something in the Grove setup is not working as expected, or when a user asks to diagnose or troubleshoot their Grove installation
Use when multiple independent tasks need to be executed in parallel, each in an isolated workspace with warm build state
Use when starting feature work that needs isolation from the current workspace, or before executing implementation plans in a Grove-enabled repository