audit-config

Audit configuration files, plugin manifests, and knowledge repositories for drift and broken references.

16|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/mikeprasad/aria-knowledge --skill audit-config-mikeprasad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-config
Source: https://github.com/mikeprasad/aria-knowledge/tree/main/plugin/skills/audit-config
Command: npx skills add https://github.com/mikeprasad/aria-knowledge --skill audit-config-mikeprasad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit project configuration and documentation to detect drift, staleness, and broken references across CLAUDE.md files, plugin manifests, and knowledge repositories.

Core Features & Use Cases

  • Scan CLAUDE.md files for references, version claims, and cross-links to surface drift and stale content.
  • Validate local configuration files and plugin manifests to identify broken paths, ghost configs, and outdated references.
  • Provide actionable findings with severity levels and remediation steps for session start checks or user-initiated audits.

Quick Start

Run the audit to check CLAUDE.md files, configs, and knowledge for drift, staleness, and broken references.

Frequently Asked Questions about audit-config

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

FAQPage Schema
How do I detect configuration drift and broken references in CLAUDE.md files?

Configuration drift is detected by scanning CLAUDE.md files for version claims, cross-links, and stale references, producing actionable findings ranked by severity.

What is the best way to validate plugin manifests and local config files for outdated paths?

Validating plugin manifests and config files involves checking for broken paths, ghost configs, and outdated references, then reporting issues with severity levels and remediation steps.

Can I automatically run config and documentation audits at the start of a session?

Config and documentation audits can run automatically on session starts when cadence thresholds are exceeded, or manually via user requests to check for drift and staleness.

Does the config audit process require manual approval before fixing broken references?

The audit process requires explicit user approval before applying remediation to fix detected drift, staleness, or broken references in project configuration and documentation.

Why do my knowledge repository files show broken links and stale content during project updates?

Knowledge repository files show broken links and staleness due to configuration drift during updates, detectable by auditing references and surfacing outdated content with severity rankings.