organize-root-files

Route root Markdown files to memos, docs, or devops/docs directories.

4|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/samjhecht/wrangler --skill organize-root-files
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organize-root-files
Source: https://github.com/samjhecht/wrangler/tree/main/skills/organize-root-files
Command: npx skills add https://github.com/samjhecht/wrangler --skill organize-root-files

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Markdown files at project root can become disorganized junk. This Skill scans the root for candidate markdown files (especially ALL_CAPS.md and RCA-*.md variants), analyzes their purpose, and routes them to the appropriate directories (memos/, docs/, devops/docs/) or deletes obsolete content, following CLAUDE.md guidelines.

Core Features & Use Cases

  • Discovery of root markdown candidates and initial categorization
  • Obsolete files deletion, memoization, documentation, or devops documentation
  • Consistent naming conventions when moving to memos or docs
  • Phase-based actions aligned with CLAUDE.md guidance

Quick Start

  • Announce action: "🔧 Using Skill: organize-root-files | [context]"

Frequently Asked Questions about organize-root-files

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

FAQPage Schema
How do I organize markdown files scattered across my project root?

Route root markdown files to appropriate directories by analyzing their content and purpose. This Skill discovers candidates like ALL_CAPS.md and RCA-*.md variants, classifies them as memos, documentation, or devops content, moves files with consistent naming (date prefixes for memos, lowercase-dash for docs), and generates an audit report of all actions taken.

What markdown files at the root level should be moved or deleted?

Target ALL_CAPS.md files and prefixed variants (RCA-*, ANALYSIS-*, IMPLEMENTATION-*, SUMMARY-*, NOTES-*, DESIGN-*, INVESTIGATION-*.md). The Skill analyzes each file's purpose and metadata, then routes obsolete content for deletion, memos to memos/, documentation to docs/, and devops documentation to devops/docs/.

Can I automate root markdown cleanup without manual file sorting?

Yes. This Skill automates discovery, content analysis, and classification of root markdown files, eliminating manual sorting. It applies CLAUDE.md guidelines for phase-based routing, creates target directories as needed, applies naming conventions automatically, and produces a complete audit report.

How do I maintain consistent naming when moving markdown files to subdirectories?

The Skill enforces consistent conventions: memos receive date-prefixed filenames, docs receive lowercase-dash filenames. When moving files to memos/, docs/, or devops/docs/, the Skill renames them according to destination conventions and creates directories if they don't exist.

What happens to obsolete markdown files during root cleanup?

Obsolete content identified during analysis can be deleted as part of the routing process. The Skill evaluates each file's purpose and metadata against CLAUDE.md guidelines, determines whether to delete, memoize, or document it, then executes the appropriate action with full audit trail.

Does this work with existing documentation structure in memos/ and docs/?

Yes. The Skill discovers and respects existing memos/ and docs/ directories, creates them if missing, and routes files into them following established naming patterns. It integrates with existing devops/docs/ structure and applies phase-based actions aligned with your project's CLAUDE.md guidelines.