garbage-collector

Plan and execute approved local cleanup with preview and undo logs.

325|60|Updated Apr 20, 2026

Search Tags:#automation #logs #safety #cleanup #preview #undo #local-files

Ready to run

npx skills add https://github.com/Prompthon-IO/agent-systems-handbook --skill garbage-collector-prompthon-io

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: garbage-collector
Source: https://github.com/Prompthon-IO/agent-systems-handbook/tree/main/skills/garbage-collector
Command: npx skills add https://github.com/Prompthon-IO/agent-systems-handbook --skill garbage-collector-prompthon-io

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Local cleanup tasks can be dangerous when performed without previews, clear rules, and explicit approval. This skill demonstrates a cautious, preview-first workflow that explains findings, requires user consent, and keeps logs to support undo where possible.

Core Features & Use Cases

Preview-first workflow: scan target directories, produce a readable report, and propose actions before any changes.
Explicit approval: cleanup actions are executed only after clear user confirmation.
Deterministic scripts and logs: actions are generated via a deterministic helper and all steps are logged for traceability and undo.
Safety boundaries: bounds on scan targets and explicit handling of destructive actions to prevent unintended harm.
Extensible rules and quarantine: initial rule store available and reversible actions (e.g., moving to a quarantine area) to support undo scenarios.

Quick Start

Run the preview workflow and inspect the plan before applying any cleanup.

Frequently Asked Questions about garbage-collector

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

FAQPage Schema

How do I safely clean up local files in my Downloads folder without accidentally deleting important data?▼

Safe local file cleanup requires a preview-first workflow that scans target directories, generates a readable report of proposed actions, and executes deletion only after explicit user approval. This approach uses deterministic scripts and maintains undo-ready logs to support reversing actions.

What is a preview-first cleanup workflow and how does it prevent unintended data loss?▼

A preview-first cleanup workflow explains scan findings and proposes actions before making any changes. It enforces safety boundaries on scan targets and requires explicit user consent, ensuring destructive local file actions are handled carefully to prevent unintended harm.

Can I undo local cleanup actions if I realize I still need the files?▼

Yes, local cleanup actions can be undone because the workflow logs all steps for traceability and uses reversible actions like moving files to a quarantine area. This undo-ready design ensures you can recover items if a deletion was premature.

How do I apply custom cleanup rules to automate local file organization?▼

You can automate local file organization by loading custom cleanup rules from a CSV rule store. The system applies these rules during the directory scan to generate a deterministic cleanup plan tailored to your specific workspace requirements.

Does the cleanup script support permanent deletion or does it only move files to quarantine?▼

The cleanup script supports both reversible quarantine and permanent deletion. It applies actions with an optional permanent-delete flag, allowing you to choose between moving files to a quarantine area for undo purposes or executing irreversible destruction.

What are the limitations of using automated scripts for workspace cleanup tasks?▼

Automated workspace cleanup scripts have safety boundaries that limit scan targets to common areas like Downloads and Trash. They are constrained by explicit handling of destructive actions, meaning they cannot operate outside approved targets without clear user confirmation.