Clean Build Artifacts

Remove common build artifact folders with optional dry-run preview.

27|8|Updated Jan 16, 2026

Search Tags:#build #workspace #artifacts #PowerShell #gitignore #disk-space #clean

Ready to run

npx skills add https://github.com/Sounder25/Google-Antigravity-Skills-Library --skill clean-build-artifacts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Clean Build Artifacts
Source: https://github.com/Sounder25/Google-Antigravity-Skills-Library/tree/main/04_clean_artifacts
Command: npx skills add https://github.com/Sounder25/Google-Antigravity-Skills-Library --skill clean-build-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build artifacts can accumulate and cause disk bloat and subtle build errors. This skill removes ignored build artifacts to reclaim space and keep workspaces lean.

Core Features & Use Cases

Remove common artifact folders across languages (bin, obj, node_modules, pycache, .venv)
Safe mode with optional dry-run and explicit target lists
Logs detailing deleted paths and a final space-reclamation summary

Quick Start

To start, run a dry-run to preview deletions: clean artifacts --dry-run Then perform the actual cleanup: clean artifacts --target bin obj node_modules pycache .venv

Frequently Asked Questions about Clean Build Artifacts

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

FAQPage Schema

How do I safely clean build artifacts like bin and node_modules to free up disk space?▼

You can safely clean build artifacts by running a dry-run preview first, then executing a recursive deletion with explicit targets like bin, obj, node_modules, and __pycache__ to reclaim disk space without touching source code.

What is the best way to remove ignored build directories across multiple programming languages?▼

The best way to remove ignored build directories across languages is to use a cleanup tool that supports explicit targets for common folders like bin, obj, .venv, and __pycache__, ensuring safe recursive deletion without affecting source files.

Can I preview which files will be deleted before cleaning workspace artifacts?▼

Yes, you can preview deletions by using the dry-run mode. This allows you to see exactly which build artifact paths will be removed and view a space-reclamation summary before performing the actual cleanup.

Does artifact cleanup support Python virtual environments and cache folders?▼

Yes, artifact cleanup supports Python projects by explicitly targeting and removing __pycache__ directories and .venv virtual environments, alongside other language-specific build folders like node_modules and bin.

Why should I use explicit targets when deleting build artifacts instead of wiping the whole workspace?▼

Using explicit targets when deleting build artifacts ensures safe recursive deletion by strictly limiting cleanup to specified folders like obj and node_modules, preventing accidental deletion of your source code and project configuration files.