skills.rest
I-Synergy
I-SynergyOFFICIAL
Explore all skills by this author →
GitHub

verify-config

Audit CLAUDE.md and .claude/reference files against codebase patterns to detect documentation drift.

1|Updated Mar 17, 2026
Search Tags:#documentation#codebase#verification#audit#claude#patterns#drift
One-click install
npx skills add https://github.com/I-Synergy/I-Synergy.NugetPackageManager --skill verify-config
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-config
Source: https://github.com/I-Synergy/I-Synergy.NugetPackageManager/tree/main/.claude/skills/verify-config
Command: npx skills add https://github.com/I-Synergy/I-Synergy.NugetPackageManager --skill verify-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits CLAUDE.md and .claude/reference files against actual codebase conventions to detect drift and ensure documentation stays in sync with the codebase.

Core Features & Use Cases

  • Drift detection: compares documented conventions with real code patterns across the CLAUDE toolset.
  • Coverage: validates CLAUDE.md and .claude/reference files against sample code references to surface gaps and inconsistencies.
  • Reporting: generates a structured findings report highlighting Correct, Drift, Missing, and Stale items.

Quick Start

Implement an automated drift audit by comparing the current documentation against the codebase referenced patterns.

Frequently Asked Questions about verify-config

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

FAQPage Schema
How do I detect documentation drift against my codebase?▼

To detect documentation drift, you can audit CLAUDE.md and .claude/reference files against actual codebase patterns. This process identifies inconsistencies by comparing documented naming conventions and folder structures with real code samples.

What is the best way to verify documented conventions against code patterns?▼

Verifying documented conventions against code patterns requires auditing CLAUDE.md files alongside actual repository references. This comparison surfaces gaps, missing mappings, and stale entries, producing a structured findings report for review.

How do I audit CLAUDE.md files for missing mappings and stale entries?▼

Auditing CLAUDE.md files for missing mappings and stale entries involves comparing the documented rules against real code samples. The audit checks naming conventions and folder structure, generating a structured report highlighting drift.

Does documentation drift detection work with .claude/reference files?▼

Yes, documentation drift detection works directly with .claude/reference files. It validates these files against sample code references to surface coverage gaps, missing mappings, and stale entries within the CLAUDE toolset.

What does a documentation drift audit report include?▼

A documentation drift audit report includes structured findings categorized as Correct, Drift, Missing, and Stale items. It highlights where documented conventions match or diverge from the actual codebase patterns.

When should I run a codebase verification audit for documentation drift?▼

You should run a codebase verification audit when CLAUDE.md or .claude/reference files are updated or codebase patterns change. This ensures documentation stays in sync by identifying drift, missing mappings, and stale entries.

Related Skills

Explore More Software Engineering Skills→
robit-manrobit-man

skill-builder

Transform extracted documentation into structured Claude skill packages with SKILL.md files.

Community
Advanced
benkrugerbenkruger
25

flow-doc-sync

Compare code behavior against documentation and generate a severity-tagged drift report.

Community
Intermediate
ravenoakravenoak

weed

Detect divergences between Allium specifications and implementation code.

Community
Advanced
mjamoremjamore

repo-docs

Synchronize repository documentation with source code using doc-first workflows.

Community
Advanced