clean-project

Name: clean-project
Availability: InStock
Author: jupitlunar

Remove unused files and reorganize documentation with git-backed backups.

Updated Aug 23, 2026

Ready to run

npx skills add https://github.com/JupitLunar/website --skill clean-project

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-project
Source: https://github.com/JupitLunar/website/tree/main/.agent/skills/clean-project
Command: npx skills add https://github.com/JupitLunar/website --skill clean-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers streamline project maintenance by removing unused files, reorganizing documentation, and tidying the repository structure, saving time and reducing confusion.

Core Features & Use Cases

Cleanup & Backup: Create a solid plan, verify Git status, and backup before changes, ensuring safe cleanup.
Root & Organization: Move non-essential Markdown files into docs/ and consolidate temp scripts, while standardizing directories.
Dead Code & References Cleanup: Identify orphaned components, unused assets, and empty directories to prune.

Quick Start

Run a git status check and commit or stash changes.
Identify candidate files for relocation or removal using heuristic checks and move them to docs/ or scripts/temp/.
Validate the repo by running tests and building to ensure no regressions.

Frequently Asked Questions about clean-project

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

FAQPage Schema

How do I clean up unused files and reorganize my project repository?▼

To clean up a project, you need to verify Git status, create a backup, and then use heuristic checks to identify unused files for relocation or removal. The process requires explicit user confirmation before applying any destructive changes to your project repository.

What is the best way to prune dead code and consolidate documentation in a legacy codebase?▼

The best way to prune dead code and consolidate documentation in a legacy codebase is to identify orphaned components and empty directories, then move non-essential Markdown files into a docs directory to standardize the repository structure safely.

Can I use this project cleanup approach for codebases of any size?▼

Yes, this project cleanup approach applies to codebases of any size where legacy clutter obscures maintenance. It handles root cleanup, dead code pruning, and documentation consolidation regardless of your repository scale.

Do I need Git to remove dead code and tidy documentation safely?▼

Yes, you need Git to remove dead code and tidy documentation safely because this cleanup process requires git-backed backups. You must run a git status check and commit or stash changes before identifying candidate files for relocation or removal.

How do I ensure no regressions after removing orphaned components and unused assets?▼

To ensure no regressions after removing orphaned components and unused assets, you must validate the repository by running tests and building the project immediately after moving candidate files to docs or scripts/temp directories.