Expected: Invoking the skill runs the sandbox-sync bash block (the fenced script that mkdir's ~/repo-search-storage and resets each cached repo to its remote HEAD) automatically as part of loading the skill.
Actual: In a session with auto-mode permissions active, that embedded bash block was denied outright by the Claude Code auto-mode classifier ("Blocked by classifier"), likely due to the loop over ~/repo-search-storage/*/ combined with git reset --hard / git clean -fdx -- even though it is scoped to the skill's own read-only sandbox and never touches the user's project.
Workaround used: Skipped the skill's built-in sync step and ran a manual git clone --depth 1 / via the Bash tool directly, which was permitted without a prompt.
Context: Happened while looking up the GSD (Get Shit Done) Claude Code plugin's statusline script for UI-formatting reference. Not a one-off -- the same classifier reasoning would presumably block the skill's sync step for any user running in auto mode, since the requested action never changes.
Possible fixes:
- Split the destructive git reset --hard / git clean -fdx sync out of the always-run fenced block into something the classifier can more easily recognize as sandbox-scoped/safe.
- Document a manual-clone fallback in SKILL.md for when the sync block is denied, so the agent does not have to improvise one.
Expected: Invoking the skill runs the sandbox-sync bash block (the fenced script that mkdir's ~/repo-search-storage and resets each cached repo to its remote HEAD) automatically as part of loading the skill.
Actual: In a session with auto-mode permissions active, that embedded bash block was denied outright by the Claude Code auto-mode classifier ("Blocked by classifier"), likely due to the loop over ~/repo-search-storage/*/ combined with git reset --hard / git clean -fdx -- even though it is scoped to the skill's own read-only sandbox and never touches the user's project.
Workaround used: Skipped the skill's built-in sync step and ran a manual git clone --depth 1 / via the Bash tool directly, which was permitted without a prompt.
Context: Happened while looking up the GSD (Get Shit Done) Claude Code plugin's statusline script for UI-formatting reference. Not a one-off -- the same classifier reasoning would presumably block the skill's sync step for any user running in auto mode, since the requested action never changes.
Possible fixes: