Skip to main content
skill CX Codex

plonge — Claude Code skill: cache cleanup and installation

plonge is a Claude Code skill that finds caches, dependencies, and build output. It starts when storage is low or a build fails with no space left on device.

MIT ★ 260 updated 2026-11-17

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mattt/plonge --skill plonge -a claude-code
Open on GitHub

What plonge does

The plonge skill checks free space, reports project and global caches, then prepares a cleanup plan. It starts with plonge disk and a scan, lists the largest caches, and separates prune rules from clear rules. Running clean without --apply removes nothing.

Project and global cleanup use separate commands, plonge clean and plonge clean --global. Before applying either selection, the skill asks for approval and reports the paths and estimated space to recover. Active and busy projects are filtered by activity data and process checks. When paseo is missing from PATH, the busy-agent check has no protection; when its status cannot be read, every project is treated as busy.

What it helps with

  • locate caches that consume disk space
  • investigate a no space left on device build failure
  • report project and global cache sizes
  • preview cleanup without deleting files
  • remove stale dependencies and build output after approval

Example prompts for the agent

  • Check free space and find the largest caches.
  • Run a dry cleanup for project caches and show the selected paths.
  • After approval, clean global caches with the same selection options.

How to install plonge

1Skills CLI (Vercel)

npx skills add mattt/plonge --skill plonge -a claude-code

2Manually: put the files in place

~/.claude/skills/plonge/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/plonge/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about plonge

How do I install plonge in Claude Code?

Run npx skills add mattt/plonge --skill plonge -a claude-code. The skill file is then available at ~/.claude/skills/plonge/SKILL.md.

What does plonge do?

plonge checks free space, reports project and global caches, shows their sizes, and prepares cleanup actions. Deletion requires --apply after the dry run is approved.

What does plonge need to work?

paseo must be available on PATH for the busy-agent check. If its status cannot be read, projects are treated as busy and project cache cleanup does not proceed.

Source text

SKILL.md · MIT
---
name: plonge
description: Find and clean developer caches, downloaded dependencies, and build output. Use when disk space is low, a build fails with "no space left on device", or the user asks to clean caches, node_modules, virtual environments, or tool downloads.
---

# Plonge

Plonge reports project caches and global caches outside projects.
A cache is a directory or set of files selected by a cleanup rule.
Project roots come from mise's record of loaded config files,
or from CLI `--root` options.
`scan` and `clean` without `--apply` delete nothing.

If the Plonge MCP server is available, use its `scan`, `clean`, and `disk` tools.
MCP parameters have the same meaning as the corresponding CLI options,
but MCP does not support `--root` or `--no-mise`.

## Steps

1. Check free space with `plonge disk`.
   It reports space on the home directory's volume on macOS and Linux.

2. Scan before cleanup.
   Include global caches for a report of both project and global caches.

   ```console
   plonge scan --global
   ```

3. Show the largest caches, their sizes, and the totals.
   A quiet project has known activity at least `quiet_hours` old
   (24 hours by default).
   An active project has more recent or unknown activity.
   A busy project has a running or initializing Paseo agent.
   Plonge refuses a project cache that a running process uses
   and names the process in the report.
   Project cleanup excludes busy projects and, by default, active projects.
   Say which global rules are `prune` and which are `clear`.
   A `prune` rule uses the tool's policy to select unused or stale data.
   A `clear` rule can remove cached data still in use;
   later commands may need to download dependencies or rebuild files.
   Global cleanup does not use the project activity or Git checks.

4. Run a dry run and show the output.
   Project and global cleanup are separate operations:

   ```console
   plonge clean
   plonge clean --global
   ```

5. Get the user's approval of the dry run before `--apply`.
   State the selected paths or actions and the estimated space to recover.
   Do not promise that the whole reported size will become free space.
   A size marked `(whole cache)` is a prune rule's whole cache;
   say that the tool removes only part of it.
   Keep the approved selection options when you apply the cleanup.

   ```console
   plonge clean --apply
   plonge clean --global --apply
   ```

6. Report the estimated space freed, the change in free space
   on the home directory's volume that the same output gives,
   and any skipped or failed cleanup.
   Other processes can also change free space, so do not call the change exact.

## Selection options

Get approval for these options as part of the dry run:

- `--include-active` selects active projects, but still excludes busy projects.
- `--include-clear` with `--global` selects clear rules.
- `--min-size 100MiB` skips project caches smaller than 100 MiB.

`--global` cannot be combined with `--include-active`, `--min-size`,
`--root`, or `--no-mise`.

Project activity is based on Git HEAD timestamps, Claude transcripts,
and Paseo status, not on uncommitted edits or running builds.
If `paseo` is not on PATH, the busy check cannot see Paseo agents and gives no protection.
If `paseo` is on PATH but its status cannot be read, every project counts as busy,
so `clean` deletes no project caches until Paseo works again.
The running-process check sees only processes that run when Plonge checks;
it does not see a stopped service or a later cron job.
If Plonge cannot list the processes, every project counts as busy.
Do not clean caches in a project that you know is busy.

Do not use another deletion command to bypass a skipped path or rule.
Check the reported reason and explain it to the user.

© mattt · MIT · mattt/plonge

Similar skills

All skills for DevOps and infrastructure →

Project sponsors

Companies that keep this analytics open