Does this skill automatically change my files?

No, it follows a strict five-step workflow where actual changes are only applied during the final stage after a preview and explicit 'yes' confirmation from the user.

How can I revert changes made by the organizer?

While the skill maintains an audit log, the safest practice is to commit your current work to Git before running the organizer; this allows you to use 'git reset --hard' to undo any changes instantly.

Will it delete my environment variables or git history?

No, the skill includes a predefined 'Protected File Patterns' list that automatically excludes sensitive items like .env files, .git folders, and dependency locks from any modification.

Can I customize which files are protected?

Yes, you can edit the PROTECTED_PATTERNS list within the script to include custom directories or specific file extensions that should never be moved or deleted.

What happens during a dry run?

A dry run simulates all operations and validates safety checks without actually touching the file system, reporting exactly what would happen if the execution were real.

Safe Project Organizer

Name: Safe Project Organizer
Author: ananddtyagi

byananddtyagi

•

625

생산성 및 워크플로

Safely analyzes and reorganizes project structures using multi-stage validation and dry-run previews to ensure codebase integrity.

소개

The Safe Project Organizer is a specialized skill for Claude Code designed to help developers standardize and clean up messy project directories without the risk of breaking functionality. It identifies misplaced documentation, empty directories, and non-standard layouts, offering a structured workflow that progresses from read-only scans to explicit user-confirmed executions. By strictly adhering to safety protocols—including the protection of sensitive files like .env and system folders like .git or node_modules—it allows for confident architectural refactoring of file systems during project handoffs, migrations, or general maintenance.

주요 기능

Automated protection for version control, dependencies, and sensitive credentials
Detailed dry-run previews with impact metrics and risk level classification
625 GitHub stars
Comprehensive audit logging for every operation performed
Explicit user confirmation requirement for all real file system modifications
Read-only analysis phase to identify issues without making changes

사용 사례

Cleaning up cluttered project roots by organizing documentation and config files into standard directories
Standardizing legacy codebase structures to modern patterns before adding new features
Safe removal of empty directories and temporary files to prepare for project handoff

소개

주요 기능

Automated protection for version control, dependencies, and sensitive credentials
Detailed dry-run previews with impact metrics and risk level classification
625 GitHub stars
Comprehensive audit logging for every operation performed
Explicit user confirmation requirement for all real file system modifications
Read-only analysis phase to identify issues without making changes

사용 사례

Cleaning up cluttered project roots by organizing documentation and config files into standard directories
Standardizing legacy codebase structures to modern patterns before adding new features
Safe removal of empty directories and temporary files to prepare for project handoff