Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From famdeck-toolkit
Control how toolkit-init treats individual git repos — set a project to "normal" (full init), "readonly" (Atlas registration only), or "ignore" (skip entirely). Trigger when the user wants to exclude or limit a specific project from toolkit initialization, check what mode a project is in, or list modes across repos. Do NOT trigger for general init operations, relay config, or environment modes unrelated to toolkit init behavior.
How this skill is triggered — by the user, by Claude, or both
Slash command
/famdeck-toolkit:toolkit-modeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Control how `/toolkit-init` treats a project via `.git/info/toolkit-mode`.
Control how /toolkit-init treats a project via .git/info/toolkit-mode.
| Mode | Effect |
|---|---|
| normal | Full init — Atlas, Relay, Beads, Agent Mail, Serena, BMAD |
| readonly | Atlas registry only (no files written). For reference repos |
| ignore | Completely skipped by init scans |
Parse the user's intent from $ARGUMENTS:
.git/ exists in $CWD, error if not a git repo.git/info/toolkit-mode — if missing, mode is normalnormal | readonly | ignore — set mode.git/ exists in $CWDnormal: remove .git/info/toolkit-mode if it existsreadonly / ignore: mkdir -p .git/info && echo "<mode>" > .git/info/toolkit-mode--list — show all projects and their modes.git/info/toolkit-mode in eachnpx claudepluginhub ivintik/private-claude-marketplace --plugin famdeck-toolkitSwitches between projects in a monorepo configured via .groundwork.yml, setting active project context and showing spec status.
Scans a root directory for existing git repos and worktrees, then manages default repos used as context in interviews.
Sets or queries the active workspace directory using Brokk's activateWorkspace and getActiveWorkspace tools. Required before code intelligence on new projects or repository switches.