Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
chrisbanes avatar

Grove Doctor

  • 9 installs
  • 20 repo stars
  • Updated February 25, 2026
  • chrisbanes/grove

Runs diagnostic checks on a Grove setup (platform, CLI, config, golden copy, workspace dir, hooks) and prints a pass/warn/fail report with fixes.

About

Runs an ordered set of diagnostic checks on a Grove installation and prints a full report with remediation steps. A developer uses it when Grove is not working as expected or to troubleshoot workspace issues.

  • Checks APFS platform, CLI version, config, golden-copy cleanliness, and hooks
  • Every FAIL includes a concrete fix command

Grove Doctor by the numbers

  • 9 all-time installs (skills.sh)
  • Ranked #1,020 of 1,435 DevOps & CI/CD 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 grove-doctor

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs9
repo stars20
Last updatedFebruary 25, 2026
Repositorychrisbanes/grove

What it does

Runs diagnostic checks on a Grove setup (platform, CLI, config, golden copy, workspace dir, hooks) and prints a pass/warn/fail report with fixes.

Files

SKILL.mdMarkdownGitHub ↗

I'm using the grove-doctor skill to run a series of diagnostic checks on this Grove setup.

Workflow

Run each check in order. Collect all results and print the full report at the end.

Check 1: Platform

diskutil info / | grep "File System"
  • PASS if output contains APFS
  • WARN if macOS but not APFS
  • FAIL if not macOS

Check 2: CLI installed

command -v grove
  • PASS if a path is returned
  • FAIL if the command is not found. Fix: follow the installation instructions at https://github.com/chrisbanes/grove

Check 3: CLI version

grove version
  • PASS — record the version string for the report
  • FAIL if the command errors. Fix: reinstall the CLI

Check 4: Grove initialized

test -f .grove/config.json
  • PASS if the file exists
  • FAIL if not found. Fix: run the grove:grove-config skill to initialize Grove in this repository

Check 5: Golden copy health

git status --porcelain
git rev-parse --abbrev-ref HEAD
git rev-parse --short HEAD
  • PASS if git status --porcelain produces no output (clean)
  • WARN if there are uncommitted changes — report the count of dirty files. Suggestion: commit or stash changes before creating workspaces
  • Record branch name and short commit hash in the report regardless

Check 6: Workspace directory

Read workspaceDir from .grove/config.json. Then:

test -d <workspaceDir> && test -w <workspaceDir>
df -h <workspaceDir>
  • PASS if the directory exists, is writable, and has available disk space
  • WARN if free space is under 5 GB
  • FAIL if the directory does not exist or is not writable. Fix: mkdir -p <workspaceDir> or adjust permissions

Check 7: Hooks

test -x .grove/hooks/post-clone
  • PASS if the file exists and is executable
  • FAIL if missing or not executable. Fix: chmod +x .grove/hooks/post-clone

Check 8: Active workspaces

grove list --json
  • PASS — report the count of active workspaces
  • Flag any workspaces whose created_at is more than 7 days ago as potentially stale
  • FAIL if the command errors

Output Format

After all checks, print the report:

Grove Doctor Report:
  [PASS] Platform: macOS (APFS)
  [PASS] CLI: grove v0.1.0
  [PASS] Initialized: .grove/config.json found
  [WARN] Golden copy: 3 uncommitted changes
  [PASS] Workspace dir: /tmp/grove/myproject (12GB free)
  [FAIL] Hooks: .grove/hooks/post-clone not executable
         Fix: chmod +x .grove/hooks/post-clone
  [PASS] Workspaces: 2 active

For every FAIL, include a Fix line with a specific command or actionable suggestion. For every WARN, include a Suggestion line.

Quick Reference

CheckCommand
Platform`diskutil info /
CLI installedcommand -v grove
CLI versiongrove version
Initializedtest -f .grove/config.json
Golden copygit status --porcelain
Workspace dirdf -h <workspaceDir>
Hookstest -x .grove/hooks/post-clone
Workspacesgrove list --json

Common Mistakes

  • Running grove-doctor outside a git repo — checks 4 and 5 will produce misleading results. Always run from the repository root.
  • Reporting only failures — always print the full checklist including PASSes so the user can see what is healthy.
  • Skipping the fix command — every FAIL must include a concrete remediation step, not just a description of the problem.

Red Flags

  • Multiple FAILs starting from Check 2 — the CLI is not installed; later checks are meaningless. Stop early and fix the CLI first.
  • Golden copy is on a detached HEAD — workspaces created from it will have no branch context.
  • Workspace directory is on a non-APFS volume — CoW clones will not work; Grove requires APFS.

Integration

  • Standalone — invoked manually when things go wrong; not called by other skills automatically

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.