lfe-hygiene

Audit repository compliance with the Library-First Engineering framework.

43|2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lfe-hygiene
Source: https://github.com/StChiotis/Library-First-Engineering/tree/main/.agents/skills/lfe-hygiene
Command: npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill ensures that the repository maintains compliance with the Library-First Engineering framework by conducting structural audits to detect "Documentation Drift" or "Spaghetti Files."

Core Features & Use Cases

  • Repository Audit: Checks for "Illegal" and "Ghost" files, ensuring all registered files are present and vice versa.
  • Coordination Layer Audit: Verifies the coordination layer between the Library and the filesystem.
  • State Audit: Ensures pipeline_status.md and CONTEXT.md accurately reflect the repository's state.
  • History Audit: Checks CHANGELOG.md for compliance with the 7-milestone rolling window and session count accuracy.
  • Skills Audit: Validates SKILL.md files and .agents/permissions.json.
  • Scaling Audit: Ensures .docs/ directories and files meet size and organization requirements.
  • Coordination Contract Audit: Checks for drift between the coordination contract and actual skill operations.
  • Retention Check: Manages aged-out entries in the hot file and moves them to the cold file.
  • Output Generation: Writes .plans/hygiene_report.md with findings.

Quick Start

Run the /lfe-hygiene command to initiate the hygiene audit.

Frequently Asked Questions about lfe-hygiene

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

FAQPage Schema
What is a Library-First Engineering structural audit?

A Library-First Engineering structural audit verifies repository compliance by checking file system integrity, coordination layers, state verification, history compliance, skills validation, scaling standards, contract adherence, and retention management.

How do I audit my repository for documentation drift and ghost files?

Run an LFE hygiene audit to detect documentation drift and spaghetti files. The audit identifies illegal and ghost files, ensuring all registered files are present in the filesystem and vice versa.

How do I verify my repository's pipeline status and context state compliance?

Conduct a state audit to verify that pipeline_status.md and CONTEXT.md accurately reflect the repository's state. This ensures the coordination layer between the Library and the filesystem remains synchronized.

What does a changelog history compliance check cover for repository hygiene?

A history compliance audit checks CHANGELOG.md against a 7-milestone rolling window and verifies session count accuracy to maintain proper repository history retention and tracking standards.

Can I use this to manage aged-out hot file entries in my repository?

Yes, the retention check manages aged-out entries in the hot file and moves them to the cold file. This retention management ensures scaling standards are met across .docs/ directories.

Where do I find the results after running a repository hygiene audit?

The repository hygiene audit writes its findings to .plans/hygiene_report.md. This output file contains the structural audit results covering file integrity, state verification, and contract adherence.