repo-hygiene

Audit Git repositories for root hygiene and Markdown front-matter compliance.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/ManfronEnrico/thesis-manifold --skill repo-hygiene-manfronenrico
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-hygiene
Source: https://github.com/ManfronEnrico/thesis-manifold/tree/main/.claude/skills/repo-hygiene
Command: npx skills add https://github.com/ManfronEnrico/thesis-manifold --skill repo-hygiene-manfronenrico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repository root hygiene is critical for discoverability and automation. This audit ensures Markdown docs and rootfiles conform to a minimal-root policy, with valid YAML front matter and correct placement.

Core Features & Use Cases

  • Emits a structured compliance report for root and docs cleanliness, enabling quick remediation planning.
  • Proposes and applies only approved or safe fixes to bring the repository into compliance.
  • Useful during onboarding, handovers, and periodic maintenance to keep docs discoverable and machine-readable.

Quick Start

Analyze the repository root to produce a compliance report and, if safe, apply planned fixes.

Frequently Asked Questions about repo-hygiene

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

FAQPage Schema
How do I audit a Git repository for root-level hygiene and Markdown front-matter completeness?

A repository hygiene audit scans root files and Markdown docs to validate root allowlists and YAML front-matter completeness, generating a structured compliance report with a remediation plan for safe, reversible fixes.

What is a minimal-root policy for Markdown docs and how does an audit enforce it?

A minimal-root policy restricts root-level files to an approved allowlist to ensure discoverability. An audit enforces it by validating root file placement and Markdown front matter, producing a remediation plan with safe fixes.

How do I validate YAML front matter in Markdown docs during repository maintenance?

Validate YAML front matter in Markdown docs by running a repository audit that checks metadata completeness and correct file placement, outputting a compliance report that flags missing or invalid front matter for remediation.

Can I automate repository hygiene fixes without risking breaking changes to my docs?

Yes, you can automate repository hygiene fixes safely. The audit proposes and applies only approved, reversible fixes to root files and Markdown docs, ensuring metadata validation and allowlist corrections do not break existing content.

When do I need to run a repository root and Markdown compliance audit?

Run a repository compliance audit during project onboarding, team handovers, and periodic maintenance to ensure Markdown docs remain machine-readable, root files conform to allowlists, and overall repository hygiene is maintained.

What limitations should I expect when automating root file allowlist and Markdown metadata fixes?

The audit is limited to applying only safe, reversible fixes for root allowlists and Markdown front-matter validation, meaning complex structural doc rewrites or non-standard YAML metadata may require manual remediation outside the automated plan.