project-cleanup

Automate project documentation cleanup and folder reorganization via shell commands.

Updated Oct 12, 2025
One-click install
npx skills add https://github.com/IDEA-on-Action/IDEA-on-Action --skill project-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-cleanup
Source: https://github.com/IDEA-on-Action/IDEA-on-Action/tree/main/.claude/skills/project-cleanup
Command: npx skills add https://github.com/IDEA-on-Action/IDEA-on-Action --skill project-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

복잡한 프로젝트에서 문서와 폴더 구조가 무질서하게 흩어져 관리가 어렵다. 이 스킬은 SSDD 원칙에 따라 오래된 문서를 아카이브하고, 불필요 파일과 빈 폴더를 제거해 유지보수를 간소화한다.

Core Features & Use Cases

  • 아카이브 규칙 제시: 문서 크기 기준과 아카이브 경로를 정의한다.
  • 삭제/정리 규칙: 불필요 파일, 빈 폴더, 임시 파일 제거를 돕는다.
  • Use Case: CLAUDE.md의 히스토리를 archive로 분리하고, 3개월 이상 된 daily-summaries를 아카이브한다.

Quick Start

CLAUDE.md 히스토리를 docs/archive로 이동하고, 불필요 파일( backup, tmp 등) 제거를 시작합니다.

Frequently Asked Questions about project-cleanup

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

FAQPage Schema
How do I automatically clean up and reorganize project documentation?

Project cleanup automates reorganization of documentation and folder structures by enforcing size guidelines, archiving outdated content, and consolidating duplicates across daily summaries, phase plans, and completed-todos files using shell commands and standard file operations.

Can I archive old documentation files and remove unnecessary folders?

Yes. The Skill applies archive rules based on document size and age criteria, moves outdated content to designated archive paths, removes unnecessary files and empty folders, and supports cleanup of backup and temporary files across your project structure.

What files and folders does project cleanup work with?

Project cleanup operates on CLAUDE.md, roadmap.md, changelog.md, and project-todo.md files, plus daily summaries, phase plans, and completed-todos directories, using Read, Bash, Grep, Glob, Write, and Edit tools for shell-based operations.

How does the SSDD principle help manage complex project documentation?

SSDD enforces systematic organization by archiving documents older than defined thresholds like three months, removing redundant and temporary files, and consolidating duplicates, which simplifies long-term maintenance and reduces manual sorting across large documentation sets.

What's the best way to prevent documentation clutter in ongoing projects?

Apply automated cleanup workflows that enforce size limits, archive outdated daily summaries and phase records on a schedule, consolidate duplicate entries, and remove empty folders, which maintains a lean structure without manual intervention.