claude-settings-audit

Generate read-only Claude Code settings.json allowlists from repository tech stack analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill analyzes a repository to produce a minimal, read-only settings.json allowlist and optional .mcp.json suggestions for Claude Code, reducing manual audit work and preventing unsafe permission grants.

Core Features & Use Cases

  • Tech stack detection: inspects lockfiles and common config files to identify languages, package managers, build and infra tools, and monorepo layouts.
  • Service and framework checks: detects integrations such as Sentry, Docker, Terraform, and major web frameworks to include appropriate WebFetch domains and skill suggestions.
  • Safe, minimal recommendations: generates a read-only permissions.allow list scoped to detected tools and provides merge instructions when existing .claude/settings.json is present.

Quick Start

Ask the skill to analyze the repository and produce a ready-to-copy .claude/settings.json allowlist and any recommended .mcp.json entries.

Frequently Asked Questions about claude-settings-audit

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

FAQPage Schema
How do I generate read-only permissions for Claude Code settings.json?

You can generate read-only permissions for Claude Code by analyzing your repository's lockfiles and config files to produce a minimal settings.json allowlist of safe bash commands, skill access, and WebFetch domains.

What is a read-only allowlist for Claude Code and when do I need it?

A read-only allowlist for Claude Code is a scoped set of safe permissions in settings.json that prevents unsafe grants. You need it during new project setups, repository audits, and CI/PR reviews to ensure secure AI interactions.

How do I set up Claude Code permissions for a monorepo with multiple package managers?

To set up Claude Code permissions for a monorepo, the tool detects monorepo layouts, languages, and package managers from lockfiles to recommend a unified read-only bash command allowlist and appropriate skill access settings.

Does the Claude settings audit detect framework and service integrations like Sentry or Docker?

Yes, the audit detects services and frameworks like Sentry, Docker, and Terraform by checking configuration files, then includes the appropriate WebFetch domains and skill suggestions in the generated settings.json allowlist.

Can I merge new read-only permissions into an existing .claude/settings.json file?

Yes, when an existing .claude/settings.json file is present, the audit provides specific merge instructions to safely integrate the newly detected read-only permissions without overwriting your current configuration.

What are the limitations of using automated repository audits for MCP and settings.json generation?

The main limitation of automated settings.json generation is that it relies on detecting known lockfiles and config files, meaning custom or obscure infrastructure tools may be missed and require manual permission additions.