claude-settings-audit

# 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: ```bash 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` ...