mpm-organize

Organize repository files into a navigable structure with git-backed backups.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill mpm-organize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mpm-organize
Source: https://github.com/bobmatnyc/claude-mpm-marketplace/tree/main/plugins/claude-mpm/skills/mpm-organize
Command: npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill mpm-organize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages growing codebases and documentation by automatically organizing files, consolidating duplicates, and pruning stale content. It helps teams keep projects navigable, reduces manual cleanup, and preserves history through safe movements.

Core Features & Use Cases

  • Pattern Detection: Scans for project organizational standards and existing artifacts to guide structuring.
  • Consolidation: Merges duplicates and redundant docs.
  • Pruning: Removes stale or unused files while archiving candidates.
  • Categorization: Sorts docs into research/user/developer.
  • Safe Movement: Uses git mv to preserve history and requires backups.
  • Backup: Creates a backup tarball before applying changes.

Quick Start

Run /mpm-organize to automatically consolidate, prune, and reorganize your project files according to the predefined structure.

Frequently Asked Questions about mpm-organize

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

FAQPage Schema
How do I automatically organize project files and prune stale code in my repository?

The tool enforces safe file movement by using `git mv` to preserve version history and automatically creates a backup tarball before applying any structural changes to your project.

What is the best way to consolidate duplicate documentation in a growing codebase?

You can automatically categorize documentation into research, user, and developer groups, consolidating redundant files and archiving stale candidates to keep your project navigable.

Does this project organization approach work with existing git repositories?

Yes, it works with existing git repositories by enforcing safe file movements with `git mv` and requiring backup tarballs to preserve your source history during consolidation and pruning.

What happens to protected files when automatically pruning a repository?

Protected files are preserved during the pruning process, and the tool logs all consolidation and pruning operations to ensure critical configuration and source code are not removed.