storage-reclaim

Identify and reclaim disk space from build artifacts, caches, and temporary files.

60|13|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/plurigrid/asi --skill storage-reclaim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: storage-reclaim
Source: https://github.com/plurigrid/asi/tree/main/skills/storage-reclaim
Command: npx skills add https://github.com/plurigrid/asi --skill storage-reclaim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly identify and reclaim disk space by locating space hogs such as build artifacts, git garbage, and temporary files, enabling safe cleanup.

Core Features & Use Cases

  • Broad scans: Quick global disk usage probes to surface large directories.
  • Targeted cleanups: Safe removal of common culprits (target/, node_modules, venvs, pycache).
  • Parallel investigation: Guidance for running checks in parallel to speed up cleanup.

Quick Start

Run the quick-start commands to scan a directory, identify the largest folders, and remove or clean as needed. Start with a broad scan (du -sh /path/*) and drill into the biggest dirs before deleting.

Frequently Asked Questions about storage-reclaim

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

FAQPage Schema
How do I reclaim disk space from node_modules and build artifacts?

Reclaim disk space by identifying and safely removing space hogs like node_modules, target directories, and __pycache__ folders. Start with a broad scan using du -sh to find the largest directories, then remove regeneratable artifacts like build outputs and package caches. The Skill guides parallel checks across Rust targets, Node modules, Python venvs, and Docker images to speed cleanup.

What's the safest way to clean up git garbage and temporary files?

Git garbage and temporary files accumulate over time, consuming significant disk space. Use git count-objects to measure waste and git gc to reclaim it safely. The Skill handles verification checks before deletion, ensuring cleanup steps are reversible and regeneratable through standard commands like npm install or cargo clean.

Can I clean up Rust targets, Python venvs, and Docker images at the same time?

Yes, parallel discovery and cleanup work across multiple build systems and environments. The Skill scans Rust targets, Node modules, Python virtual environments, Julia artifacts, hidden caches, Docker images, and Homebrew leftovers in a single pass. Run verifiable checks in parallel to speed up the process when disk space is near capacity.

How do I know which files are safe to delete when reclaiming storage?

Safe cleanup targets regeneratable artifacts: build outputs (cargo clean, npm install, pip install), git garbage (git gc), and package manager leftovers (brew cleanup, docker system prune). The Skill provides verifiable checks and safe deletion procedures, allowing you to restore files by rebuilding or reinstalling without data loss.

When should I clean up disk space in CI environments?

CI environments accumulate build artifacts and caches that consume disk space, especially when capacity runs low. The Skill covers both local development and CI contexts, identifying and removing space hogs across dependency caches, temporary build files, and container images using safe, parallel checks before deletion.

What's the difference between removing build artifacts versus deleting cache files?

Build artifacts (target/, node_modules, __pycache__) are regeneratable by running build commands; cache files like hidden caches and git garbage are cleaned by specific tools (git gc, brew cleanup). The Skill distinguishes between safe targets and handles each with appropriate removal or cleanup commands to avoid data loss.