audit-settings

Audit global, project, and local CLAUDE settings for conflicts and overrides.

2|Updated Dec 20, 2020
One-click install
npx skills add https://github.com/buvis/home --skill audit-settings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-settings
Source: https://github.com/buvis/home/tree/main/.claude/skills/audit-settings
Command: npx skills add https://github.com/buvis/home --skill audit-settings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits configuration across global, project, and local levels to uncover conflicts, redundant overrides, and permission escalations that complicate governance.

Core Features & Use Cases

  • Detect cross-level conflicts and redundant overrides to ensure consistent behavior across scopes.
  • Flag unknown or suspicious keys and permission escalations for remediation.
  • Provide actionable remediation guidance for configuration governance and MCP server consistency.

Quick Start

Assess your current CLAUDE config by running this audit to surface inconsistencies and recommended fixes.

Frequently Asked Questions about audit-settings

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

FAQPage Schema
How do I detect conflicts in multi-level CLAUDE settings?

Detect conflicts in multi-level CLAUDE settings by running an audit that merges global and per-project overrides to surface redundant configurations and unknown keys across user, project, and repository scopes.

What is the best way to audit permissions escalations across project and local config scopes?

Auditing permissions escalations across project and local config scopes requires a multi-level comparison that identifies overridden settings and flags suspicious permission changes for remediation.

Can I get remediation guidance for unknown keys found during a config audit?

Remediation guidance for unknown keys found during a config audit is provided directly by the multi-level comparison, which flags suspicious keys and offers actionable steps to resolve configuration inconsistencies.

Why does my local CLAUDE config override my global project settings?

Local CLAUDE config overrides global project settings due to multi-level configuration hierarchy rules, and a cross-level audit can surface these exact redundant overrides to help you manage governance.