claude-settings-audit

# Agent command policy audit ## Contract | Field | Bound contract | |---|---| | Trigger | User sets up a project, audits agent command permissions, or asks which read-only bash commands and domains to allow | | Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. | | Side effect | Emits a recommended command and domain allowlist as chat output. Writes nothing to disk | | Done | A validated, least-privilege command and domain policy recommendation containing only read-only, project-relevant commands and domains, with no state-modifying commands | ## Inputs - The repository root to audit (defaults to the current working directory). - Optional: an existing policy file to merge into. ## Procedure 1. Parse repository manifests to identify the tech stack. List the repository root and find manifest files to depth 2 (`*.toml`, `*.json`, `*.lock`, `*.yaml`, `*.yml`, `Makefile`, `Dockerfile`, `*.tf`). Classify by indicator files: - 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`, `kubernetes/`, `helm/` - Monorepo: `lerna.json`, `nx.json`, `turbo.json`, `pnpm-workspace.yaml` Done whe...