klh-settings-audit

Generates recommended Claude Code settings.json permissions by detecting a repository's tech stack.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/klh/skills --skill klh-settings-audit-klh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: klh-settings-audit
Source: https://github.com/klh/skills/tree/main/.well-known/agent-skills/klh-settings-audit
Command: npx skills add https://github.com/klh/skills --skill klh-settings-audit-klh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Configuring Claude Code permissions manually is tedious and error-prone: you must know which read-only bash commands are safe to allow, which package manager the project uses, and which documentation domains to whitelist. This Skill automates that audit by scanning the repository and producing a ready-to-use settings.json. ## Core Features & Use Cases - Tech Stack Detection: Scans for indicator files (pyproject.toml, package.json, go.mod, Cargo.toml, lock files) to identify languages, frameworks, package managers, and monorepo tools. - Permission Generation: Builds an allow list of read-only bash commands (git, gh CLI, package manager queries) matched strictly to the detected stack, excluding state-modifying commands. - MCP & WebFetch Suggestions: Recommends Sentry or Linear MCP server configs for .mcp.json and framework-specific documentation domains for WebFetch. - Use Case: When onboarding a new Python/Django project, run the audit to instantly get a settings.json allowing poetry, git, and gh read commands plus docs.djangoproject.com fetches, without hand-writing any JSON. ## Quick Start Analyze this repository and generate a recommended Claude Code settings.json with read-only permissions for the detected tech stack.

Frequently Asked Questions about klh-settings-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Claude Code settings.json permissions automatically?

Run the settings audit on your repository: it detects your tech stack from files like package.json, pyproject.toml, and lock files, then outputs a complete settings.json with read-only bash command permissions matched to your tools.

What commands are safe to allow in Claude Code permissions?

Only read-only commands that cannot modify state, such as ls, cat, git status, git log, gh pr view, and package manager queries like npm list or poetry show. Never allow install, build, run, write, or delete commands.

Does the audit support monorepos and multiple languages?

Yes, it detects monorepo tools like lerna.json, nx.json, turbo.json, and pnpm-workspace.yaml, and can identify multiple language ecosystems in one repository, generating permissions for each detected stack.

Why does the audit exclude npm commands when pnpm-lock.yaml exists?

The audit only includes the package manager actually used by the project, determined by its lock file. Including alternative managers would grant unnecessary permissions and could cause agents to use the wrong tool.

Can the audit configure MCP servers for Sentry or Linear?

Yes, when Sentry SDK or Linear usage is detected, it suggests MCP server entries for .mcp.json, including the Sentry HTTP endpoint and the Linear MCP server with an API key environment variable.