Help us improve
Share bugs, ideas, or general feedback.
From cadence-guardrails
Use when configuring git-guardrails with your GitHub identity after install or update. Self-destructs after setup so it reappears when the plugin updates.
npx claudepluginhub cameronsjo/workbench --plugin cadence-guardrailsHow this skill is triggered — by the user, by Claude, or both
Slash command
/cadence-guardrails:guardrails-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Configure git-guardrails by detecting the user's GitHub identity and writing the required environment variables to `~/.claude/settings.json`.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Configure git-guardrails by detecting the user's GitHub identity and writing the required environment variables to ~/.claude/settings.json.
Check current state - Read ~/.claude/settings.json and check if CADENCE_ALLOWED_OWNERS already exists in the env block. If configured, show current values and ask if the user wants to reconfigure or exit. (Legacy GIT_GUARDRAILS_ALLOWED_OWNERS / GIT_GUARDRAILS_ALLOWED_REPOS keys are no longer read by the binary as of cadence-hooks 0.8.0 — offer to migrate them if present.)
Detect GitHub identity - Run gh api user --jq .login to get the authenticated GitHub username. If gh is not installed or not authenticated, ask the user to provide their GitHub username manually via AskUserQuestion.
Ask for additional owners - Use AskUserQuestion:
Ask for allowed repos - Use AskUserQuestion:
CADENCE_ALLOWED_REPOS emptyowner/repo listWrite to settings.json - Read ~/.claude/settings.json, add/update these keys in the env block:
CADENCE_ALLOWED_OWNERS — space-separated list of GitHub users/orgsCADENCE_ALLOWED_REPOS — space-separated list of owner/repo pairs (only if the user provided any)GIT_GUARDRAILS_ALLOWED_OWNERS or GIT_GUARDRAILS_ALLOWED_REPOS keys exist, remove them after copying their values forward.Verify - Read back the settings.json and confirm the values were written correctly. Show the user what was set.
Self-destruct - After successful configuration:
~/.claude/plugins/cache/*/git-guardrails/commands/guardrails-init.mdSummary - Show what was configured and remind the user:
git push and gh write operations against repos outside the allowed list~/.claude/settings.json env block~/.claude/settings.json under the env key, NOT as shell exportsCADENCE_ALLOWED_OWNERS is REQUIRED — hooks block all pushes/writes if unsetCADENCE_ALLOWED_REPOS is OPTIONAL — only needed for collaborator/org reposGIT_GUARDRAILS_ALLOWED_* — if the user is on an older binary, keep the legacy names until they upgrade (brew upgrade cadence-hooks)gh CLI is unavailable, fall back to manual input — don't fail