Agent skill · data analytics · sickn33
claude-settings-audit
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.
Why this skill is useful
Generates specific `settings.json` permissions based on detected tech stack and tooling, which the AI wouldn't reliably infer on its own.
What it needs
Requires bash installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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: 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 Phase 4: Generate Recommendations Build the allow list by combining: Baseline Commands (Always Include) Stack-Specific Commands Only include commands for tools actually detected in the project. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/claude-settings-audit