safe-project-organizer

Analyze and reorganize project directory structures with dry-run previews and protected file patterns.

688|85|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/ananddtyagi/cc-marketplace --skill safe-project-organizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safe-project-organizer
Source: https://github.com/ananddtyagi/cc-marketplace/tree/main/plugins/claude-dev-infrastructure/skills/safe-project-organizer
Command: npx skills add https://github.com/ananddtyagi/cc-marketplace --skill safe-project-organizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Messy project roots, scattered documentation files, and empty directories make codebases hard to navigate, but manually reorganizing files risks breaking imports, deleting important data, or corrupting version control state.

Core Features & Use Cases

  • Multi-Stage Safe Workflow: Progress through read-only scan, analysis, detailed preview, dry-run simulation, and confirmed real execution with an audit log.
  • Protected Pattern Enforcement: Automatically excludes version control directories, dependencies, lock files, environment secrets, and build artifacts from any modification.
  • Risk-Classified Suggestions: Each move, delete, or create-directory operation is labeled low, medium, or high risk with explicit safety checks.
  • Use Case: Before handing off a project to a new team, run the organizer to consolidate scattered Markdown files into docs/, remove empty directories, and create standard folders like src/ and tests/—all verified through a dry run before any real change.

Quick Start

Ask Claude to scan your project structure and suggest safe organizational improvements with a preview before making any changes.

Frequently Asked Questions about safe-project-organizer

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

FAQPage Schema
How do I safely reorganize a messy project structure?

Run the project organizer script with the --scan flag first for a read-only analysis, then use --analyze and --preview to review suggestions. Only use --execute-real after confirming the dry-run output looks correct.

How to preview file moves before actually moving them?

Use the --preview flag to see every suggested move, delete, and directory creation with exact source and destination paths. The --execute flag then simulates all operations as a dry run without touching the filesystem.

What files are protected from project reorganization?

Protected patterns include .git and other version control directories, node_modules and vendor dependencies, .env and credential files, lock files like package-lock.json, and build output directories like dist and build.

Can I undo changes made by a project organizer script?

Yes, if the project is committed to version control, use git checkout or git reset to restore the previous state. The script also writes a .project_organizer.log audit file recording every executed operation.

Why does the organizer skip some directories during cleanup?

Directories are skipped when they match protected patterns, are not actually empty, or fail safety checks such as containing version control markers. Skipped operations are reported in the results summary with their reasons.