agent-md-refactor

Refactor bloated agent instruction files into a minimal root with linked documentation.

Updated Nov 29, 2025
One-click install
npx skills add https://github.com/thimslugga/agent-skills --skill agent-md-refactor-thimslugga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-md-refactor
Source: https://github.com/thimslugga/agent-skills/tree/main/skills/agent/agent-md-refactor
Command: npx skills add https://github.com/thimslugga/agent-skills --skill agent-md-refactor-thimslugga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactor bloated agent instruction files into a minimal root and organized, linked documentation.

Core Features & Use Cases

  • Progressive disclosure: keep essentials in root; move detailed guidelines to linked files.
  • Automated file structure: create a minimal root file plus categorized files under a dedicated directory.
  • Verification and deletion flagging: identify redundant or vague instructions for removal.

Quick Start

Refactor my AGENTS.md or CLAUDE.md to a minimal root with linked, categorized files.

Frequently Asked Questions about agent-md-refactor

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

FAQPage Schema
How do I refactor a bloated AGENTS.md or CLAUDE.md file?

To refactor a bloated AGENTS.md or CLAUDE.md file, extract essential instructions into a minimal root file and move detailed guidelines into linked, categorized topic files under a dedicated directory. This progressive disclosure structure keeps agent instructions streamlined and organized.

What is progressive disclosure for agent instruction files?

Progressive disclosure for agent instruction files is an architecture pattern that keeps only essential guidelines in the root file while moving detailed documentation to linked files. It minimizes root file size and organizes instructions into a small set of categorized topics.

How do I organize linked documentation files extracted from a monolithic agent instruction file?

You organize linked documentation files by categorizing the remainder of extracted instructions into a small set of topic files under a dedicated directory. The process involves identifying contradictions, extracting root essentials, categorizing the remainder, creating the file structure, and flagging deletions.

When should I restructure my COPILOT.md or AGENTS.md into linked files?

You should restructure your COPILOT.md or AGENTS.md into linked files when the monolithic file has grown unwieldy, contains contradictions, or requires progressive disclosure to maintain instruction clarity. The refactoring process flags redundant or vague instructions for removal.

Can I identify redundant or vague instructions before splitting my agent documentation?

Yes, you can identify redundant or vague instructions before splitting agent documentation. The refactoring process explicitly flags potential deletions and identifies contradictions during the initial phase before extracting essentials and categorizing the remainder into linked files.

Does this refactoring approach work for any monolithic agent instruction format?

Yes, this refactoring approach works for any monolithic agent instruction format like AGENTS.md, CLAUDE.md, or COPILOT.md. It applies progressive disclosure to extract essentials into a minimal root and categorize the remainder into linked topic files.