repository-docs-governance

Audit and restructure AGENTS.md hierarchies, codemaps, and documentation indexes for repositories.

Updated Aug 16, 2026
One-click install
npx skills add https://github.com/Aveer/skills --skill repository-docs-governance-aveer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repository-docs-governance
Source: https://github.com/Aveer/skills/tree/main/skills/repository-docs-governance
Command: npx skills add https://github.com/Aveer/skills --skill repository-docs-governance-aveer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repository instruction files like AGENTS.md, READMEs, and codemaps drift over time, accumulating stale, duplicated, or misplaced guidance that wastes context and confuses both humans and AI agents. This Skill audits, migrates, and refreshes the entire documentation governance system so critical rules stay always-on while reference material lives in authoritative on-demand locations. ## Core Features & Use Cases - Three Operating Modes: Audit (inspect and recommend without editing), Migration (implement an accepted redistribution of instructions), and Refresh (sync documentation claims with current repository reality). - Classification Model: Routes every rule to its correct home, whether root AGENTS.md, nested guides, codemaps, task-specific skills, or architecture docs, and removes duplicated or superseded content. - Verification Contract: Validates SKILL.md frontmatter, checks referenced paths exist, tests skill discovery with opencode debug, and confirms no critical invariant depends only on optional skill loading. - Use Case: A repository's root AGENTS.md has grown to hundreds of lines mixing safety invariants with stale route lists and duplicated catalogs. Run an audit to classify each section, then migrate topology facts to the codemap and procedures into focused skills while preserving every critical rule. ## Quick Start Audit this repository's AGENTS.md files, codemaps, and documentation indexes, then recommend a governance restructure without making any edits.

Frequently Asked Questions about repository-docs-governance

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

FAQPage Schema
How do I audit a repository's AGENTS.md files for stale content?▼

Run the audit mode to inspect root and nested AGENTS.md files, codemaps, and doc indexes without editing. It classifies each section, flags drift-prone content like exact counts and dated paths, and reports duplication findings with a migration plan.

What is the best way to reduce a bloated AGENTS.md file?▼

Classify each rule by kind: keep only universal invariants and safety boundaries in the root file, move topology facts to a codemap, extract task procedures into small skills, and delete duplicated or superseded text. Never optimize for line count at the expense of safety rules.

When should repository instructions become a skill instead of staying in AGENTS.md?▼

Move content to a skill only when it forms a coherent task category with clear literal triggers. Invariants needed before any action must stay in AGENTS.md, since skills load on demand and critical rules cannot depend on optional loading.

Does this skill edit files during an audit?▼

No. Audit mode inspects and recommends changes without editing anything. Edits only happen in migration mode after a redistribution plan is accepted, or in refresh mode when updating stale facts against current repository evidence.

How do I verify a documentation governance migration worked?▼

Check the final diff and untracked files, verify all referenced local paths exist, validate every SKILL.md frontmatter name and description, and run opencode debug skill --pure when available to prove native skill discovery.