skills.rest
rinti
rintiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

settings-audit

Analyze a repository to propose read-only Claude Code settings.json permissions.

Updated Apr 3, 2015
Search Tags:#tech stack#Claude Code#monorepo#analyze#read-only#settings.json#repo audit
One-click install
npx skills add https://github.com/rinti/dotfiles --skill settings-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: settings-audit
Source: https://github.com/rinti/dotfiles/tree/main/claude/skills/settings-audit
Command: npx skills add https://github.com/rinti/dotfiles --skill settings-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes a repository to propose Claude Code settings.json permissions, ensuring only read-only commands are allowed and consistent configurations for new projects or audits.

Core Features & Use Cases

  • Detect tech stack, project structure, and build tools to tailor a safe settings.json.
  • Generate a baseline and stack-specific allowlists for Claude Code based on repository indicators.
  • Identify monorepo patterns and existing .claude/settings.json to propose appropriate changes.
  • Provide a ready-to-apply settings payload for Claude Code in settings.json.

Quick Start

Run the settings-audit skill on your repository to generate the recommended Claude Code settings.json permissions.

Frequently Asked Questions about 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 in settings.json?▼

To generate read-only permissions for Claude Code, analyze your repository to detect the tech stack, build tools, and service integrations. This produces a structured settings.json payload with baseline and stack-specific allowlists that enforce safe, read-only operations.

Can I audit an existing .claude/settings.json configuration in a monorepo?▼

Yes, you can audit an existing .claude/settings.json configuration in a monorepo. The process identifies monorepo patterns and existing settings to propose appropriate changes, tightening permissions to read-only commands tailored to your specific project structure.

What is the best way to restrict Claude Code from modifying files during a repo audit?▼

The best way to restrict modifications during a repo audit is to apply a generated settings.json allowlist. By detecting project indicators, you can generate baseline and stack-specific commands that ensure Claude Code only executes read-only operations.

Does the settings audit work for new projects without an existing tech stack setup?▼

Yes, the settings audit works for new projects. It detects available tech stack indicators and build tools to generate a safe baseline allowlist, providing a ready-to-apply settings payload for Claude Code even when configurations are minimal.

How are build tools and service integrations detected for the Claude Code allowlist?▼

Build tools and service integrations are detected by analyzing repository indicators and project structure. This detection tailors the settings.json allowlist, generating stack-specific commands that align with the technologies identified during the repository audit.

Related Skills

Explore More Software Engineering Skills→
securityreviewaisecurityreviewai

project-overview-analysis

Analyzes Git repositories to produce summaries of their structure, risks, and key components.

Official
Intermediate
klhklh
1

claude-settings-audit

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

Community
Intermediate
wpankwpank
11

turborepo

Configure Turborepo build tasks, caching, and CI/CD pipelines for monorepos.

Community
Advanced
mkusakamkusaka
7

update-config-description

Configure Claude Code harness settings.json hooks, permissions, and environment variables.

Community
Intermediate