reclaim-disk

Measure disk usage and reclaim space from Rust and Docker caches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/neon-law-foundation/navigator --skill reclaim-disk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reclaim-disk
Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/reclaim-disk
Command: npx skills add https://github.com/neon-law-foundation/navigator --skill reclaim-disk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps recover space on a crowded development machine when builds fail, the workspace runs out of disk, or Rust and Docker caches have grown too large.

Core Features & Use Cases

  • Measures disk usage before deleting anything so cleanup starts with the biggest real consumer.
  • Reclaims Rust workspace space in safe stages, from incremental build cache removal to registry cache cleanup and full cargo clean when needed.
  • Delegates Docker-heavy cleanup to a dedicated flow when images, build cache, or leaked test containers are the main source of disk pressure.
  • Use case: a cargo test run stops with no space left on device, and the Skill identifies whether target, .cargo, or Docker should be cleaned first.

Quick Start

Ask the assistant to measure disk usage, identify the largest workspace hog, and reclaim space using the safest cleanup stage first.

Frequently Asked Questions about reclaim-disk

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

FAQPage Schema
How do I fix "no space left on device" errors during a cargo test run?

To fix no space left on device errors during cargo test, measure disk usage to identify the largest consumer, then reclaim space by cleaning Rust target directories, Cargo caches, or Docker artifacts in safe stages.

What is the safest way to reclaim disk space from Rust build caches?

Reclaiming disk space from Rust builds happens in safe stages, starting with incremental build cache removal, advancing to registry cache cleanup, and using full cargo clean only when needed.

How do I clean up Docker disk space when images and build caches are too large?

Cleaning up Docker disk space is handled by delegating to a dedicated cleanup flow that targets images, build cache, and leaked test containers when they are the main source of disk pressure.

Can I measure disk usage before deleting Rust target directories and Cargo caches?

Yes, measuring disk usage before deleting anything ensures cleanup starts with the biggest real consumer, identifying whether the target directory, .cargo cache, or Docker should be cleaned first.

What's the best way to free up storage in an overloaded development workspace?

The best way to free up storage in an overloaded development workspace is to measure usage first, then perform staged cleanup of Rust caches and Docker artifacts with safe defaults and Docker delegation.