🇺🇸English

groove-utilities-task-install

Outcome

The configured task backend is installed and verified reachable. User is informed of what was installed and how to use it.

Acceptance Criteria

• Backend CLI is available in PATH after install
• User is shown a confirmation with the installed version or a reachability check
• No-op if tasks.backend: none

Constraints

• Read tasks.backend from .groove/index.md to determine backend
• If tasks.backend: none, print friendly no-op message and exit
• Backend install guidance:
  • beans: link to https://github.com/hmans/beans for install instructions; verify with beans version
  • linear: link to https://linear.app/docs/cli for install instructions; verify with linear --version or MCP availability
  • github: link to https://cli.github.com for install instructions; verify with gh --version
• After install, run a simple reachability check (e.g., beans version or gh auth status)
• If CLI is already installed, report current version and skip install
• If tasks: beans and .beans.yml does not exist at git root:
  • Run beans init to initialise the task store and generate .beans.yml with beans defaults
  • Derive [PROJECT_PREFIX] from the git repo name (last path component of git remote get-url origin, stripped of .git, uppercased, non-alphanumeric stripped) — e.g. groove → GRV; fall back to the directory name if no remote
  • Update the prefix: field in the generated to the derived prefix (e.g. )

Weekly Installs

44

Repository

andreadellacorte/groove

GitHub Stars

4

First Seen

8 days ago

Security Audits

Gen Agent Trust HubPassSocketPassSnykPass

Installed on

opencode44

gemini-cli44

github-copilot44

codex44

kimi-cli44

cursor44