SettingsMaintenance

Audit and clean Claude Code settings across global and project layers.

5|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/N4M3Z/forge-core --skill settingsmaintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SettingsMaintenance
Source: https://github.com/N4M3Z/forge-core/tree/main/skills/SettingsMaintenance
Command: npx skills add https://github.com/N4M3Z/forge-core --skill settingsmaintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and clean Claude Code settings across permissions, plugins, hooks, and cross-layer conflicts to reduce cruft and misconfigurations.

Core Features & Use Cases

  • Structured checks across global and project layers for permissions, plugin configuration, and hook wiring.
  • A guided 6-phase workflow (scope, inventory, audit, report, apply, verify) with cross-layer consistency checks.
  • Risk reduction through cross-layer checks and auditable edits that preserve critical tooling.

Quick Start

Choose the audit scope (global, project, or both) and run the full settings maintenance workflow to review findings and apply changes.

Frequently Asked Questions about SettingsMaintenance

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

FAQPage Schema
How do I audit Claude Code settings for permission and hook conflicts?

Auditing Claude Code settings involves running a 6-phase workflow to inventory permissions, plugin configuration, and hook wiring across global and project layers to identify cruft and resolve cross-layer conflicts.

What is the best way to clean up misconfigured Claude Code plugins and hooks?

Cleaning up misconfigured plugins and hooks requires a structured audit that checks cross-layer consistency, applies risk mitigation through auditable edits, and verifies changes to preserve critical tooling.

Can I run a settings audit across both global and project layers simultaneously?

Yes, you can select global, project, or both as the audit scope to perform structured checks across permissions, plugin configuration, and hook wiring for cross-layer consistency.

How does the cross-layer settings audit workflow ensure safe configuration edits?

The cross-layer audit workflow ensures safe edits by applying a 6-phase process—scope, inventory, audit, report, apply, verify—that performs consistency checks and mitigates risks while preserving critical tooling.

When should I run a configuration audit on my Claude Code settings files?

You should run a configuration audit when you need to reduce cruft, resolve cross-layer conflicts between global and project settings, or verify that permissions and hook wiring are correctly configured.