AI-powered file organization and context engineering that understands content, not patterns. Automatically sorts temporary scripts from permanent docs while preserving your workflow. Works with Claude Code hooks. Protects README, LICENSE, configs.
git clone https://github.com/ramakay/claude-organizer.gitClaude Organize solves the file clutter problem that occurs when Claude Code creates test scripts, debug files, and documentation at your project root despite instructions. It uses AI-powered categorization to understand file purpose from content and automatically moves files into organized directories like docs/, scripts/, and their subcategories. The tool integrates seamlessly with Claude Code via PostToolUse hooks, running automatically after file creation without requiring manual intervention. It protects critical files like README and LICENSE while reducing context bloat for improved Claude performance. This complements Claude Code best practices by ensuring consistent organization regardless of session length or CLAUDE.md configuration.
[{"step":1,"action":"Specify the directory to organize using [DIRECTORY_PATH] in the prompt. Example: '/projects/my-ai-project'.","tip":"Use absolute paths for reliability. Avoid directories with system-critical files."},{"step":2,"action":"Define cleanup rules for temporary files using [LAST_MODIFIED_DATE] and [FILE_EXTENSION]. Example: 'Last modified before 2024-01-01' or '.tmp, .bak'.","tip":"Set conservative cleanup schedules (e.g., 30 days) for critical projects to avoid data loss."},{"step":3,"action":"Run the prompt in Claude Code or a similar environment with file access permissions.","tip":"Use `claude --dir /path/to/dir` to ensure the AI has the correct context for file operations."},{"step":4,"action":"Review the report and confirm the actions. Manually intervene if needed (e.g., files misclassified as temporary).","tip":"Check the `temp/` directory before cleanup to ensure no important files are accidentally moved."},{"step":5,"action":"Set up recurring organization tasks using Claude’s automation hooks or cron jobs.","tip":"Schedule weekly runs for active projects to maintain organization without manual effort."}]
Automatically sort test scripts, debug utilities, and temporary files away from project root
Organize Claude-generated documentation into structured subdirectories by purpose (testing, analysis, troubleshooting, architecture)
Maintain clean workspace automatically during active Claude Code development sessions
Teach Claude consistent project structure patterns through organized file placement
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/ramakay/claude-organizerCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Act as claude-organizer. Review the files in [DIRECTORY_PATH]. Classify each file into one of these categories: TEMPORARY_SCRIPT, PERMANENT_DOC, CONFIG_FILE, LICENSE_FILE, README_FILE, or OTHER. For TEMPORARY_SCRIPT files, suggest a cleanup schedule based on [LAST_MODIFIED_DATE] and [FILE_EXTENSION]. For PERMANENT_DOC files, ensure they are properly indexed for future retrieval. Ignore files matching [IGNORE_PATTERN] (e.g., '.git/*'). Provide a summary of actions taken and files moved.
### claude-organizer Report for Directory: /projects/ai-assistant #### Files Analyzed: 42 **TEMPORARY_SCRIPTS (9 files)** - `temp_analyze_sentiment.py` (Last modified: 2024-05-15) → Scheduled for cleanup in 7 days. - `debug_model_output.ipynb` (Last modified: 2024-05-18) → Scheduled for cleanup in 3 days. - `experimental_rag_pipeline.py` (Last modified: 2024-05-10) → Scheduled for cleanup in 14 days. **PERMANENT_DOCS (12 files)** - `system_prompt_guidelines.md` → Indexed for retrieval. - `api_integration_specs.md` → Indexed for retrieval. - `user_study_results.pdf` → Indexed for retrieval. **CONFIG_FILES (5 files)** - `.env.local` → Protected (config file). - `claude-config.json` → Protected (config file). **LICENSE_FILES (1 file)** - `LICENSE` → Protected (license file). **README_FILES (2 files)** - `README.md` → Protected (README file). - `docs/README.md` → Protected (README file). **OTHER (13 files)** - `output.log` → No action (log file). - `scratchpad.txt` → No action (temporary note). #### Actions Taken: 1. Moved 9 temporary scripts to `/projects/ai-assistant/temp/` (auto-cleanup scheduled). 2. Indexed 12 permanent docs in the Claude Code knowledge base. 3. Protected 8 critical files from modification. #### Next Steps: - Review the `temp/` directory in 7 days to confirm cleanup. - Add `output.log` to `.claudeignore` if it’s no longer needed.
Auto-transcribe meetings and generate action items
Your one-stop shop for church and ministry supplies.
Automate your browser workflows effortlessly
Agents that listen, think and act for you.
Build beautiful, interactive API documentation effortlessly.
AI assistant built for thoughtful, nuanced conversation
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan