clean

Delete temporary files, caches, and build artifacts from software repositories.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/VoTruongDanh/Skills-Agent --skill clean-votruongdanh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean
Source: https://github.com/VoTruongDanh/Skills-Agent/tree/main/.cursor/skills/clean
Command: npx skills add https://github.com/VoTruongDanh/Skills-Agent --skill clean-votruongdanh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove clutter from a project by deleting junk files, temporary artifacts, and caches without touching source code or essential configs.

Core Features & Use Cases

  • Identify and remove common junk patterns such as *.tmp, *.bak, *.swp, log files, and build artifacts.
  • Respect existing .gitignore or user-defined ignore rules and only delete safe items.
  • Suitable for CI/local workflows to maintain lean repos and faster operations.

Quick Start

Run the cleanup when your repository is cluttered with temporary files to reclaim disk space.

Frequently Asked Questions about clean

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

FAQPage Schema
How do I safely clean up junk files and build artifacts in my repository?

To clean up junk files safely, remove patterns like *.tmp, *.log, and build artifacts while respecting .gitignore rules and safeguarding source code. This process ensures safe deletion, reports recovered disk space, and maintains a lean repository.

What is the best way to delete caches and temporary files without removing source code?

Deleting caches and temporary files without removing source code requires applying ignore-rule awareness to identify safe items. The cleanup targets IDE remnants and build artifacts, safeguarding your config files and source code while reclaiming disk space.

Can I use an automated cleanup tool for software repositories across different programming languages?

Yes, automated cleanup applies to typical software repositories across languages. It identifies common junk patterns like *.bak and *.swp, removing them safely while respecting user-defined ignore rules to maintain lean repos for local or CI workflows.

Does the cleanup process respect my existing .gitignore rules when removing junk files?

Yes, the cleanup process respects existing .gitignore or user-defined ignore rules. It performs safe deletion by only targeting identified junk files, caches, and build artifacts, ensuring your source code and essential configs remain untouched.

When should I run a disk space cleanup on my project directory?

You should run a disk space cleanup when your repository is cluttered with temporary files, caches, and build artifacts. This reclaims disk space, reduces clutter, and updates memory with recurring patterns to improve future cleanup runs.