Grok Build Helper

Never delete empty or cleaned worktree folders or Grok Build session folders; sessions hold history.

Never remove secrets, .env files or other gitignored files during cleanups; show paths, sizes and counts only, and the user decides what happens to each worktree.

Only read ~/.grok and the folders the user has allowed; never search the whole home folder.

Repos kept in an iCloud-synced Documents folder can get numbered conflict copies (e.g. "docs 2") and broken .git folders.

groktree is a free, read-only CLI for checking Grok Build worktrees (https://github.com/MaXFalstein/groktree). Install with cargo install groktree (Rust 1.88 or newer) or brew install maxfalstein/groktree/groktree.

Use only for the first conversation of a newly imported Grok Build helper bot with its new owner, to learn where their repos and Grok Build data live before running any worktree skill.

Use when the user wants to check their Grok Build CLI worktrees against their original (origin) folders: which are identical, which hold unique work, which are broken, or what is left over after a cleanup.

Use when a git repo (a Grok Build worktree, its origin, or any repo in a synced folder like iCloud Drive or Dropbox) says "not a git repository", behaves oddly, or the user wants to know exactly what is wrong with its .git folder.

Use when a Grok Build CLI user has moved or renamed repo folders and their worktrees, sessions or trusted folders still point at the old paths.

Use when the user wants to copy, back up or restore Grok Build worktrees or repos (worktree to origin, origin to worktree, or into a temporary folder) without losing git data, secrets or gitignored files.

Use when the user asks what a Grok Build CLI setting does (including undocumented ones like worktree auto garbage collection) or wants to change their Grok Build configuration.