flow-hygiene

Audit CLAUDE.md, rules, and memory for drift and contradictions.

25|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/benkruger/flow --skill flow-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-hygiene
Source: https://github.com/benkruger/flow/tree/main/skills/flow-hygiene
Command: npx skills add https://github.com/benkruger/flow --skill flow-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit the health of instruction surfaces such as CLAUDE.md, .claude/rules/*, and memory to detect drift, misplacements, and contradictions that degrade project governance.

Core Features & Use Cases

  • Drift detection: identify stale references, orphaned rules, and conflicting constraints across surfaces.
  • Structural validation: verify references point to existing files and that content matches the codebase.
  • Unified findings report: generate a grouped, actionable report by source file with clear remediation guidance.

Quick Start

Run the hygiene audit to scan CLAUDE.md, rules, and memory and generate a findings report.

Frequently Asked Questions about flow-hygiene

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

FAQPage Schema
How do I detect drift in my CLAUDE.md and rules files?

Run a hygiene audit to scan CLAUDE.md, .claude/rules/*, and memory files for stale references, orphaned content, and conflicting constraints. This generates a grouped findings report with clear remediation guidance for each discrepancy.

What is instruction corpus drift in project governance?

Instruction corpus drift occurs when CLAUDE.md, rules, and memory files accumulate stale references, orphaned content, and contradictions that degrade project governance and misalign constraints from the actual codebase.

Can I audit memory files and .claude/rules for contradictions?

Yes, you can audit memory files and .claude/rules/* for contradictions by running a structural validation that verifies file references exist and checks content alignment against the codebase across all instruction surfaces.

How do I verify structural references in a CLAUDE.md instruction corpus?

Verify structural references by scanning the instruction corpus to ensure file paths in CLAUDE.md and rules point to existing files and match the codebase. The audit classifies broken paths and misplacements as actionable discrepancies.

What is the best way to generate an actionable findings report for instruction drift?

The best way to generate a findings report for instruction drift is to run a hygiene audit that groups discrepancies by source file, classifies the structural validation issues, and outputs actionable remediation guidance for CLAUDE.md and rules.

Do I need a CLAUDE.md file to run an instruction hygiene audit?

You need projects containing CLAUDE.md, .claude/rules/*, and memory files to run the hygiene audit. The scanner requires these instruction surfaces to perform surface inventory, structural verification, and discrepancy classification.