Claude Settings Audit
Analyze this repository and generate recommended Claude Code settings.json permissions for read-only commands.
When to Use
- You are setting up or auditing Claude Code
settings.json permissions for a repository.
- You need to infer a safe read-only allow list from the repo's tech stack, tooling, and monorepo structure.
- You want to review or replace an existing Claude permissions baseline with something evidence-based.
Phase 1: Detect Tech Stack
Run these commands to detect the repository structure:
ls -la
find . -maxdepth 2 \( -name "*.toml" -o -name "*.json" -o -name "*.lock" -o -name "*.yaml" -o -name "*.yml" -o -name "Makefile" -o -name "Dockerfile" -o -name "*.tf" \) 2>/dev/null | head -50
Check for these indicator files:
| Category |
Files to Check |
| Python |
pyproject.toml, setup.py, requirements.txt, Pipfile, poetry.lock, uv.lock |
| Node.js |
package.json, package-lock.json, yarn.lock, pnpm-lock.yaml |
| Go |
go.mod, go.sum |
| Rust |
Cargo.toml, Cargo.lock |
| Ruby |
Gemfile, Gemfile.lock |
| Java |
pom.xml, build.gradle, build.gradle.kts |
| Build |
Makefile, Dockerfile, docker-compose.yml |
| Infra |
*.tf files, kubernetes/, helm/ |
| Monorepo |
lerna.json, nx.json, turbo.json, pnpm-workspace.yaml |
Phase 2: Detect Services
Check for service integrations:
| Service |
Detection |
| Sentry |
sentry-sdk in deps, @sentry/* packages, .sentryclirc, sentry.properties |
| Linear |
Linear config files, .linear/ directory |
Read dependency files to identify frameworks:
package.json → check dependencies and devDependencies
pyproject.toml → check [project.dependencies] or [tool.poetry.dependencies]
Gemfile → check gem names
Cargo.toml → check [dependencies]
Phase 3: Check Existing Settings
cat .claude/settings.json 2>/dev/null || echo "No existing settings"
Phase 4: Generate Recommendations
Build the allow list by combining:
Baseline Commands (Always Include)
[
"Bash(ls:*)",
"Bash(pwd:*)",
"Bash(find:*)",
"Bash(file:*)",
"Bash(stat:*)",
"Bash(wc:*)",
"Bash(head:*)",
"Bash(tail:*)",
"Bash(cat:*)",
"Bash(tree:*)",
"Bash(git status:*)",
"Bash(git log:*)",
"Bash(git diff:*)",
"Bash(git show:*)",
"Bash(git branch:*)",
"Bash(git remote:*)",
"Bash(git tag:*)",
"Bash(git stash list:*)",
"Bash(git rev-parse:*)",
"Bash(gh pr view:*)",
"Bash(gh pr list:*)",
"Bash(gh pr checks:*)",
"Bash(gh pr diff:*)",
"Bash(gh issue view:*)",
"Bash(gh issue list:*)",
"Bash(gh run view:*)",
"Bash(gh run list:*)",
"Bash(gh run logs:*)",
"Bash(gh repo view:*)",
"Bash(gh api:*)"
]
Stack-Specific Commands
Only include commands for tools actually detected in the project.
Python (if any Python files or config detected)
| If Detected |
Add These Commands |
| Any Python |
python --version, python3 --version |
poetry.lock |
poetry show, poetry env info |
uv.lock |
uv pip list, uv tree |
Pipfile.lock |
pipenv graph |
requirements.txt (no other lock) |
pip list, pip show, pip freeze |
Node.js (if package.json detected)
| If Detected |
Add These Commands |
| Any Node.js |
node --version |
pnpm-lock.yaml |
pnpm list, pnpm why |
yarn.lock |
yarn list, yarn info, yarn why |
package-lock.json |
npm list, npm view, npm outdated |
TypeScript (tsconfig.json) |
tsc --version |
Other Languages
| If Detected |
Add These Commands |
go.mod |
go version, go list, go mod graph, go env |
Cargo.toml |
rustc --version, cargo --version, cargo tree, cargo metadata |
Gemfile |
ruby --version, bundle list, bundle show |
pom.xml |
java --version, mvn --version, mvn dependency:tree |
build.gradle |
java --version, gradle --version, gradle dependencies |
Build Tools
| If Detected |
Add These Commands |
Dockerfile |
docker --version, docker ps, docker images |
docker-compose.yml |
docker-compose ps, docker-compose config |
*.tf files |
terraform --version, terraform providers, terraform state list |
Makefile |
make --version, make -n |
Skills (for Sentry Projects)
If this is a Sentry project (or sentry-skills plugin is installed), include:
[
"Skill(sentry-skills:agents-md)",
"Skill(sentry-skills:blog-writing-guide)",
"Skill(sentry-skills:brand-guidelines)",
"Skill(sentry-skills:claude-settings-audit)",
"Skill(sentry-skills:code-review)",
"Skill(sentry-skills:code-simplifier)",
"Skill(sentry-skills:commit)",
"Skill(sentry-skills:create-branch)",
"Skill(sentry-skills:create-pr)",
"Skill(sentry-skills:django-access-review)",
"Skill(sentry-skills:django-perf-review)",
"Skill(sentry-skills:doc-coauthoring)",
"Skill(sentry-skills:find-bugs)",
"Skill(sentry-skills:gh-review-requests)",
"Skill(sentry-skills:gha-security-review)",
"Skill(sentry-skills:iterate-pr)",
"Skill(sentry-skills:pr-writer)",
"Skill(sentry-skills:security-review)",
"Skill(sentry-skills:skill-creator)",
"Skill(sentry-skills:skill-scanner)",
"Skill(sentry-skills:skill-writer)",
"Skill(sentry-skills:sred-project-organizer)",
"Skill(sentry-skills:sred-work-summary)"
]
WebFetch Domains
Always Include (Sentry Projects)
[
"WebFetch(domain:docs.sentry.io)",
"WebFetch(domain:develop.sentry.dev)",
"WebFetch(domain:docs.github.com)",
"WebFetch(domain:cli.github.com)"
]
Framework-Specific
| If Detected |
Add Domains |
| Django |
docs.djangoproject.com |
| Flask |
flask.palletsprojects.com |
| FastAPI |
fastapi.tiangolo.com |
| React |
react.dev |
| Next.js |
nextjs.org |
| Vue |
vuejs.org |
| Express |
expressjs.com |
| Rails |
guides.rubyonrails.org, api.rubyonrails.org |
| Go |
pkg.go.dev |
| Rust |
docs.rs, doc.rust-lang.org |
| Docker |
docs.docker.com |
| Kubernetes |
kubernetes.io |
| Terraform |
registry.terraform.io |
MCP Server Suggestions
MCP servers are configured in .mcp.json (not settings.json). Check for existing config:
cat .mcp.json 2>/dev/null || echo "No existing .mcp.json"
Sentry MCP (if Sentry SDK detected)
Add to .mcp.json (replace {org-slug} and {project-slug} with your Sentry organization and project slugs):
{
"mcpServers": {
"sentry": {
"type": "http",
"url": "https://mcp.sentry.dev/mcp/{org-slug}/{project-slug}"
}
}
}
Linear MCP (if Linear usage detected)
Add to .mcp.json:
{
"mcpServers": {
"linear": {
"command": "npx",
"args": ["-y", "@linear/mcp-server"],
"env": {
"LINEAR_API_KEY": "${LINEAR_API_KEY}"
}
}
}
}
Note: Never suggest GitHub MCP. Always use gh CLI commands for GitHub.
Output Format
Present your findings as:
- Summary Table - What was detected
- Recommended settings.json - Complete JSON ready to copy
- MCP Suggestions - If applicable
- Merge Instructions - If existing settings found
Example output structure:
## Detected Tech Stack
| Category | Found |
| --------------- | -------------- |
| Languages | Python 3.x |
| Package Manager | poetry |
| Frameworks | Django, Celery |
| Services | Sentry |
| Build Tools | Docker, Make |
## Recommended .claude/settings.json
\`\`\`json
{
"permissions": {
"allow": [
// ... grouped by category with comments
],
"deny": []
}
}
\`\`\`
## Recommended .mcp.json (if applicable)
If you use Sentry or Linear, add the MCP config to `.mcp.json`...
Important Rules
What to Include
- Only READ-ONLY commands that cannot modify state
- Only tools that are actually used by the project (detected via lock files)
- Standard system commands (ls, cat, find, etc.)
- The
:* suffix allows any arguments to the base command
What to NEVER Include
- Absolute paths - Never include user-specific paths like
/home/user/scripts/foo or /Users/name/bin/bar
- Custom scripts - Never include project scripts that may have side effects (e.g.,
./scripts/deploy.sh)
- Alternative package managers - If the project uses pnpm, do NOT include npm/yarn commands
- Commands that modify state - No install, build, run, write, or delete commands
Package Manager Rules
Only include the package manager actually used by the project:
| If Detected |
Include |
Do NOT Include |
pnpm-lock.yaml |
pnpm commands |
npm, yarn |
yarn.lock |
yarn commands |
npm, pnpm |
package-lock.json |
npm commands |
yarn, pnpm |
poetry.lock |
poetry commands |
pip (unless also has requirements.txt) |
uv.lock |
uv commands |
pip, poetry |
Pipfile.lock |
pipenv commands |
pip, poetry |
If multiple lock files exist, include only the commands for each detected manager.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: claude-settings-audit3description: Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.4risk: critical5source: community6date_added: "2026-03-06"7metadata:8 source: https://skillmd.com/skills/iradoweck/claude-settings-audit9---1011# Claude Settings Audit1213Analyze this repository and generate recommended Claude Code `settings.json` permissions for read-only commands.1415## When to Use16- You are setting up or auditing Claude Code `settings.json` permissions for a repository.17- You need to infer a safe read-only allow list from the repo's tech stack, tooling, and monorepo structure.18- You want to review or replace an existing Claude permissions baseline with something evidence-based.1920## Phase 1: Detect Tech Stack2122Run these commands to detect the repository structure:2324```bash25ls -la26find . -maxdepth 2 \( -name "*.toml" -o -name "*.json" -o -name "*.lock" -o -name "*.yaml" -o -name "*.yml" -o -name "Makefile" -o -name "Dockerfile" -o -name "*.tf" \) 2>/dev/null | head -5027```2829Check for these indicator files:3031| Category | Files to Check |32| ------------ | ------------------------------------------------------------------------------------- |33| **Python** | `pyproject.toml`, `setup.py`, `requirements.txt`, `Pipfile`, `poetry.lock`, `uv.lock` |34| **Node.js** | `package.json`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml` |35| **Go** | `go.mod`, `go.sum` |36| **Rust** | `Cargo.toml`, `Cargo.lock` |37| **Ruby** | `Gemfile`, `Gemfile.lock` |38| **Java** | `pom.xml`, `build.gradle`, `build.gradle.kts` |39| **Build** | `Makefile`, `Dockerfile`, `docker-compose.yml` |40| **Infra** | `*.tf` files, `kubernetes/`, `helm/` |41| **Monorepo** | `lerna.json`, `nx.json`, `turbo.json`, `pnpm-workspace.yaml` |4243## Phase 2: Detect Services4445Check for service integrations:4647| Service | Detection |48| ---------- | ------------------------------------------------------------------------------- |49| **Sentry** | `sentry-sdk` in deps, `@sentry/*` packages, `.sentryclirc`, `sentry.properties` |50| **Linear** | Linear config files, `.linear/` directory |5152Read dependency files to identify frameworks:5354- `package.json` → check `dependencies` and `devDependencies`55- `pyproject.toml` → check `[project.dependencies]` or `[tool.poetry.dependencies]`56- `Gemfile` → check gem names57- `Cargo.toml` → check `[dependencies]`5859## Phase 3: Check Existing Settings6061```bash62cat .claude/settings.json 2>/dev/null || echo "No existing settings"63```6465## Phase 4: Generate Recommendations6667Build the allow list by combining:6869### Baseline Commands (Always Include)7071```json72[73 "Bash(ls:*)",74 "Bash(pwd:*)",75 "Bash(find:*)",76 "Bash(file:*)",77 "Bash(stat:*)",78 "Bash(wc:*)",79 "Bash(head:*)",80 "Bash(tail:*)",81 "Bash(cat:*)",82 "Bash(tree:*)",83 "Bash(git status:*)",84 "Bash(git log:*)",85 "Bash(git diff:*)",86 "Bash(git show:*)",87 "Bash(git branch:*)",88 "Bash(git remote:*)",89 "Bash(git tag:*)",90 "Bash(git stash list:*)",91 "Bash(git rev-parse:*)",92 "Bash(gh pr view:*)",93 "Bash(gh pr list:*)",94 "Bash(gh pr checks:*)",95 "Bash(gh pr diff:*)",96 "Bash(gh issue view:*)",97 "Bash(gh issue list:*)",98 "Bash(gh run view:*)",99 "Bash(gh run list:*)",100 "Bash(gh run logs:*)",101 "Bash(gh repo view:*)",102 "Bash(gh api:*)"103]104```105106### Stack-Specific Commands107108Only include commands for tools actually detected in the project.109110#### Python (if any Python files or config detected)111112| If Detected | Add These Commands |113| ---------------------------------- | --------------------------------------- |114| Any Python | `python --version`, `python3 --version` |115| `poetry.lock` | `poetry show`, `poetry env info` |116| `uv.lock` | `uv pip list`, `uv tree` |117| `Pipfile.lock` | `pipenv graph` |118| `requirements.txt` (no other lock) | `pip list`, `pip show`, `pip freeze` |119120#### Node.js (if package.json detected)121122| If Detected | Add These Commands |123| ---------------------------- | -------------------------------------- |124| Any Node.js | `node --version` |125| `pnpm-lock.yaml` | `pnpm list`, `pnpm why` |126| `yarn.lock` | `yarn list`, `yarn info`, `yarn why` |127| `package-lock.json` | `npm list`, `npm view`, `npm outdated` |128| TypeScript (`tsconfig.json`) | `tsc --version` |129130#### Other Languages131132| If Detected | Add These Commands |133| -------------- | -------------------------------------------------------------------- |134| `go.mod` | `go version`, `go list`, `go mod graph`, `go env` |135| `Cargo.toml` | `rustc --version`, `cargo --version`, `cargo tree`, `cargo metadata` |136| `Gemfile` | `ruby --version`, `bundle list`, `bundle show` |137| `pom.xml` | `java --version`, `mvn --version`, `mvn dependency:tree` |138| `build.gradle` | `java --version`, `gradle --version`, `gradle dependencies` |139140#### Build Tools141142| If Detected | Add These Commands |143| -------------------- | -------------------------------------------------------------------- |144| `Dockerfile` | `docker --version`, `docker ps`, `docker images` |145| `docker-compose.yml` | `docker-compose ps`, `docker-compose config` |146| `*.tf` files | `terraform --version`, `terraform providers`, `terraform state list` |147| `Makefile` | `make --version`, `make -n` |148149### Skills (for Sentry Projects)150151If this is a Sentry project (or sentry-skills plugin is installed), include:152153```json154[155 "Skill(sentry-skills:agents-md)",156 "Skill(sentry-skills:blog-writing-guide)",157 "Skill(sentry-skills:brand-guidelines)",158 "Skill(sentry-skills:claude-settings-audit)",159 "Skill(sentry-skills:code-review)",160 "Skill(sentry-skills:code-simplifier)",161 "Skill(sentry-skills:commit)",162 "Skill(sentry-skills:create-branch)",163 "Skill(sentry-skills:create-pr)",164 "Skill(sentry-skills:django-access-review)",165 "Skill(sentry-skills:django-perf-review)",166 "Skill(sentry-skills:doc-coauthoring)",167 "Skill(sentry-skills:find-bugs)",168 "Skill(sentry-skills:gh-review-requests)",169 "Skill(sentry-skills:gha-security-review)",170 "Skill(sentry-skills:iterate-pr)",171 "Skill(sentry-skills:pr-writer)",172 "Skill(sentry-skills:security-review)",173 "Skill(sentry-skills:skill-creator)",174 "Skill(sentry-skills:skill-scanner)",175 "Skill(sentry-skills:skill-writer)",176 "Skill(sentry-skills:sred-project-organizer)",177 "Skill(sentry-skills:sred-work-summary)"178]179```180181### WebFetch Domains182183#### Always Include (Sentry Projects)184185```json186[187 "WebFetch(domain:docs.sentry.io)",188 "WebFetch(domain:develop.sentry.dev)",189 "WebFetch(domain:docs.github.com)",190 "WebFetch(domain:cli.github.com)"191]192```193194#### Framework-Specific195196| If Detected | Add Domains |197| -------------- | ----------------------------------------------- |198| **Django** | `docs.djangoproject.com` |199| **Flask** | `flask.palletsprojects.com` |200| **FastAPI** | `fastapi.tiangolo.com` |201| **React** | `react.dev` |202| **Next.js** | `nextjs.org` |203| **Vue** | `vuejs.org` |204| **Express** | `expressjs.com` |205| **Rails** | `guides.rubyonrails.org`, `api.rubyonrails.org` |206| **Go** | `pkg.go.dev` |207| **Rust** | `docs.rs`, `doc.rust-lang.org` |208| **Docker** | `docs.docker.com` |209| **Kubernetes** | `kubernetes.io` |210| **Terraform** | `registry.terraform.io` |211212### MCP Server Suggestions213214MCP servers are configured in `.mcp.json` (not `settings.json`). Check for existing config:215216```bash217cat .mcp.json 2>/dev/null || echo "No existing .mcp.json"218```219220#### Sentry MCP (if Sentry SDK detected)221222Add to `.mcp.json` (replace `{org-slug}` and `{project-slug}` with your Sentry organization and project slugs):223224```json225{226 "mcpServers": {227 "sentry": {228 "type": "http",229 "url": "https://mcp.sentry.dev/mcp/{org-slug}/{project-slug}"230 }231 }232}233```234235#### Linear MCP (if Linear usage detected)236237Add to `.mcp.json`:238239```json240{241 "mcpServers": {242 "linear": {243 "command": "npx",244 "args": ["-y", "@linear/mcp-server"],245 "env": {246 "LINEAR_API_KEY": "${LINEAR_API_KEY}"247 }248 }249 }250}251```252253**Note**: Never suggest GitHub MCP. Always use `gh` CLI commands for GitHub.254255## Output Format256257Present your findings as:2582591. **Summary Table** - What was detected2602. **Recommended settings.json** - Complete JSON ready to copy2613. **MCP Suggestions** - If applicable2624. **Merge Instructions** - If existing settings found263264Example output structure:265266```markdown267## Detected Tech Stack268269| Category | Found |270| --------------- | -------------- |271| Languages | Python 3.x |272| Package Manager | poetry |273| Frameworks | Django, Celery |274| Services | Sentry |275| Build Tools | Docker, Make |276277## Recommended .claude/settings.json278279\`\`\`json280{281"permissions": {282"allow": [283// ... grouped by category with comments284],285"deny": []286}287}288\`\`\`289290## Recommended .mcp.json (if applicable)291292If you use Sentry or Linear, add the MCP config to `.mcp.json`...293```294295## Important Rules296297### What to Include298299- Only READ-ONLY commands that cannot modify state300- Only tools that are actually used by the project (detected via lock files)301- Standard system commands (ls, cat, find, etc.)302- The `:*` suffix allows any arguments to the base command303304### What to NEVER Include305306- **Absolute paths** - Never include user-specific paths like `/home/user/scripts/foo` or `/Users/name/bin/bar`307- **Custom scripts** - Never include project scripts that may have side effects (e.g., `./scripts/deploy.sh`)308- **Alternative package managers** - If the project uses pnpm, do NOT include npm/yarn commands309- **Commands that modify state** - No install, build, run, write, or delete commands310311### Package Manager Rules312313Only include the package manager actually used by the project:314315| If Detected | Include | Do NOT Include |316| ------------------- | --------------- | -------------------------------------- |317| `pnpm-lock.yaml` | pnpm commands | npm, yarn |318| `yarn.lock` | yarn commands | npm, pnpm |319| `package-lock.json` | npm commands | yarn, pnpm |320| `poetry.lock` | poetry commands | pip (unless also has requirements.txt) |321| `uv.lock` | uv commands | pip, poetry |322| `Pipfile.lock` | pipenv commands | pip, poetry |323324If multiple lock files exist, include only the commands for each detected manager.325326## Limitations327- Use this skill only when the task clearly matches the scope described above.328- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.329- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.