chore: add setup:claude command to bootstrap Claude Code config - #131
Closed
Phanco wants to merge 1 commit into
Closed
chore: add setup:claude command to bootstrap Claude Code config#131Phanco wants to merge 1 commit into
Phanco wants to merge 1 commit into
Conversation
Adds an opt-in `npm run setup:claude` script that syncs a tracked `claude-setup/` template into a local `.claude/` directory, then registers the `zama-marketplace` and `trailofbits` plugin marketplaces and installs `zama-developer` and `building-secure-contracts`. Lets developers pick up shared skills and commands without enforcing them across the team. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
why specifically "claude" and not |
Seth-Schmidt
reviewed
May 7, 2026
| "Bash(npx hardhat test)", | ||
| "Bash(npx hardhat:*)" | ||
| ], | ||
| "ask": [ |
Contributor
There was a problem hiding this comment.
I suggest we also add some network commands to the ask list by default:
"Bash(curl:*)",
"Bash(wget:*)",
"Bash(nc:*)",
"Bash(ssh:*)",
"Bash(scp:*)",
"Bash(rsync:*)"
And maybe also some "cheat code" commands that can be used to get around the other permission blocks:
"Bash(eval:*)",
"Bash(bash -c:*)",
"Bash(sh -c:*)"
Seth-Schmidt
reviewed
May 7, 2026
| "Bash(npm run format:*)", | ||
| "Bash(npx hardhat compile)", | ||
| "Bash(npx hardhat test)", | ||
| "Bash(npx hardhat:*)" |
Contributor
There was a problem hiding this comment.
This could potentially be dangerous if a prod .env file is present in a project and claude starts running live transaction scripts. Not aware of any real examples, but just a thought. wdyt?
Contributor
There was a problem hiding this comment.
I think at least putting npx hardhat run:* and npc hardhat deploy:* into deny/ask would be preferable.
Collaborator
|
not relevant anymore, we can go back at it if needed |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
npm run setup:claudethat syncs a trackedclaude-setup/template into a local (gitignored).claude/, deep-mergingsettings.jsonon re-runs.claude-setup/settings.jsonwith marketplace + plugin config (zama-developer@zama-marketplace,typescript-lsp@claude-plugins-official,building-secure-contracts@trailofbits) plus repo-tuned npm/Hardhat permission allowlist.claude-setup/skills/andclaude-setup/commands/ready for shared skills/commands without enforcing them on developers.Closes PRO-251.
Test plan
npm run setup:claudeon a fresh checkout —.claude/is created with the synced settings and plugins..claude/settings.json— verify deep merge (template wins on conflicts, arrays unioned).building-secure-contractsskills.🤖 Generated with Claude Code