setup-matt-pocock-skills should offer to pre-configure Claude Code's tool permissions to cut down prompt fatigue #1024
JGormanAlphaSimplex
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Claude Code re-prompts for permission on lots of routine, safe operations -- reading/scanning the repo,
git status/diff/log, read-onlyghcommands (gh issue list,gh pr view, etc.) -- which gets chatty and annoying fast. Claude Code supports pre-approving these via apermissions.allow/permissions.denyblock in.claude/settings.json(a file that's committed to the repo and shared across the team), and this is exactly what's shown in the AI Coding Crash Course.I'd like
setup-matt-pocock-skillsto offer this as a new prompted section (after issue tracker / triage labels / domain docs), following the same "explore, present, confirm, write" pattern the skill already uses:.claude/orCLAUDE.mdis present in the repo (this is Claude-Code-specific; other harnesses like Copilot CLI don't currently have an equivalent repo-shareable permissions file -- Copilot CLI's approvals live per-user in~/.copilot/, not in the repo -- so the skill should skip cleanly rather than fake support for harnesses that can't actually enforce it).Read,Glob,Grep), read-only git commands (status,diff,log,show), read-onlyghcommands (issue list/view,pr list/view,apiGET calls)git push --force,git reset --hard,rm -rf, editing credential/secret files).claude/settings.json'spermissions.allow/permissions.denyarrays (the real content belongs in the settings file itself, not as markdown prose) -- with just a one-line mention added to the existing## Agent skillsblock inCLAUDE.mdnoting that permissions were pre-configured.Happy to be pointed at a better home for this if it doesn't belong in this skill specifically.
All reactions