| name | grape-usage |
| description | Explain how to use the grape Git-worktree CLI. Use when answering questions about grape commands, policy-gated rebase, safe push, worktree setup, configuration, delegated git-worktree commands, or removal safety. |
Grape Usage
Explain grape usage accurately and concisely for the user's task.
Required sources
Before answering, read the relevant canonical command reference in references/. Treat the relevant reference page as the source of truth for commands, flags, configuration, exit codes, and safety behavior. Do not rely on memory or duplicate its detailed specification in this skill.
- For command discovery and shared running or package information, read
README.md.
- For help, list, branch, remove, reset, push, rebase, init, and version questions, read
help.md, list.md, branch.md, remove.md, reset.md, push.md, rebase.md, init.md, or version.md, respectively.
- For shared strict configuration and color behavior, read
config.md and output.md.
- For unknown or delegated commands, read
git-worktree.md.
Answer workflow
- Identify whether the user needs to inspect worktrees, find a branch, safely push or policy-gated rebase the current branch, initialize configuration, add or delegate a Git worktree operation, remove worktrees, reset from configuration, or check version/help.
- Give the smallest applicable command example using
grape ....
- For reset questions, describe the relevant
grape.json fields and config lookup behavior from reset.md. Include a minimal JSON example only when it helps the user.
- For initialization questions, use the
grape init behavior in init.md.
- For unrecognized grape subcommands, explain that grape delegates them to
git worktree and give the appropriate grape invocation.
- State important prerequisites, outcomes, and limitations that apply to the requested command.
Safety
Treat grape remove and grape reset as destructive. Explain their scopes separately: remove deletes the matching worktrees and their associated local branches, while reset deletes non-default worktrees and local branches but protects the default branch and the branch checked out in the main working tree. Both commands show targets and require y or yes confirmation. Remind the user to verify the repository, prefix or regular expression, and reset configuration before proceeding. Do not imply that the main working tree or its checked-out branch can be deleted.
Treat grape push as a guarded network operation. Do not suggest unsupported push flags, custom remotes, refspecs, or protected-branch bypasses.
Treat grape rebase as a guarded history-rewriting operation. Do not suggest unsupported Git rebase flags or continuation commands through grape. Explain that conflicts remain in place and must be continued, aborted, or skipped with Git directly.
