claude-import-resource-cleanup

Find and clean abandoned processes and task resources using ownership verification rules.

Updated Aug 25, 2017
One-click install
npx skills add https://github.com/loki495/dotfiles --skill claude-import-resource-cleanup-loki495
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-import-resource-cleanup
Source: https://github.com/loki495/dotfiles/tree/main/ai/codex-skills/claude-import-resource-cleanup
Command: npx skills add https://github.com/loki495/dotfiles --skill claude-import-resource-cleanup-loki495

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Abandoned processes and leftover task resources accumulate on a development machine and consume memory, CPU, and disk space, but deleting them blindly risks killing work that is still active. This Skill applies explicit ownership and verification rules so cleanup targets are confirmed before any destructive action runs. ## Core Features & Use Cases - Abandoned Resource Detection: Identifies orphaned processes and stale task resources that no longer belong to active work. - Ownership Verification: Applies Andres's ownership rules to confirm a resource is truly abandoned before flagging it for removal. - Approval-Gated Destructive Actions: Preserves mandatory approval requirements before any deletion or termination is executed. - Use Case: After a long session of running dev servers, test suites, and background jobs, ask the assistant to find abandoned processes and safely clean them up, reviewing each target before anything is killed. ## Quick Start Ask the assistant to find abandoned processes and task resources on this machine and clean them up safely, requiring approval before any destructive action.

Frequently Asked Questions about claude-import-resource-cleanup

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

FAQPage Schema
How do I find and kill abandoned processes safely?▼

Identify candidate processes first, then verify each one is genuinely abandoned using ownership rules before terminating it. This Skill resolves exact targets and requires explicit approval before any destructive action runs, so active work is never killed by mistake.

How to clean up leftover task resources on Linux?▼

Scan for stale task artifacts and orphaned resources, confirm ownership and abandonment status for each, then remove only verified targets. The cleanup workflow delegates to the resource-cleanup rules defined in the referenced SKILL.md file.

Does this cleanup require approval before deleting resources?▼

Yes, destructive-action approval requirements are explicitly preserved. The Skill resolves exact targets first and will not execute deletions or process terminations without the required approval step.

What are the limitations of automated resource cleanup?▼

Automated cleanup depends on accurate ownership verification; resources with ambiguous ownership should be left alone rather than guessed. This Skill mitigates that risk by delegating to explicit verification rules and gating destructive actions behind approval.