agents-md:refactor

Refactor bloated AGENTS.md files into nested modular structures with context maps.

Updated May 31, 2025
One-click install
npx skills add https://github.com/dEitY719/dotfiles --skill agents-md-refactor-deity719
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-md:refactor
Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/agents-md-refactor
Command: npx skills add https://github.com/dEitY719/dotfiles --skill agents-md-refactor-deity719

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bloated AGENTS.md grows unwieldy as projects expand, making it hard to locate relevant sections or subtopics.

Core Features & Use Cases

  • Analyze the root AGENTS.md to measure length, identify inline sections, and detect opportunities for nesting.
  • Generate a plan to split content into targeted nested AGENTS.md files under appropriate subdirectories, with a concise root context.
  • Execute the plan by creating new nested files, trimming the root, and updating a Context Map for quick navigation.

Quick Start

Provide the target AGENTS.md and confirm to begin refactoring.

Frequently Asked Questions about agents-md:refactor

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

FAQPage Schema
How do I refactor a large AGENTS.md file into modular subdirectories?

To refactor a large AGENTS.md file, you can split its inline sections into targeted nested AGENTS.md files under appropriate subdirectories, keeping the root file concise with an updated context map for navigation.

When should I split my root AGENTS.md into nested files?

You should split your root AGENTS.md into nested files when the document grows bloated and unwieldy, making it hard to locate relevant sections or subtopics across multiple project modules.

What is the best way to reduce root complexity in AGENTS.md documentation?

The best way to reduce root complexity in AGENTS.md documentation is to generate a refactoring plan that moves module-specific content into nested files, keeping each nested file under 100 lines.

How do I generate a modularization plan for repo-docs like AGENTS.md?

You can generate a modularization plan for AGENTS.md by analyzing the root file to measure length, identify inline sections, and detect opportunities for nesting content within specific subdirectories.

Are there limitations on file size when reorganizing nested AGENTS.md files?

Yes, when reorganizing nested AGENTS.md files, the approach applies a limitation of keeping each newly created nested file under 100 lines to maintain readability and reduce complexity.