skill-disposable-artifact-cleanup

Audits and cleans task-owned disposable artifacts with ownership verification and delegated lifecycle routing.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/longdang193/project-OS-starter --skill skill-disposable-artifact-cleanup-longdang193
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-disposable-artifact-cleanup
Source: https://github.com/longdang193/project-OS-starter/tree/main/generated_agents/claude/skills/skill-disposable-artifact-cleanup
Command: npx skills add https://github.com/longdang193/project-OS-starter --skill skill-disposable-artifact-cleanup-longdang193

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed or interrupted workflows leave behind temporary files, worktrees, runtime sessions, and other disposable resources, and deleting the wrong ones can destroy user data, credentials, or evidence still needed for verification. ## Core Features & Use Cases - Ownership-Verified Audit Mode: Reports each candidate's exact resource identity, producer, retention dependency, cleanup owner, and eligibility without mutating anything. - Exact-Scope Direct Cleanup: Removes only explicitly authorized task-owned files or directories after re-resolving paths and blocking symlinks and reparse points. - Delegated Lifecycle Routing: Routes Herdr sessions, Git worktrees, browser profiles, and test databases to their owning workflows instead of deleting them directly. - Use Case: After a multi-agent development task finishes, audit leftover temporary traces and an unused Git worktree, clean the proven task-owned files, and route the worktree to the branch-finishing workflow for verified retirement. ## Quick Start Audit the disposable artifacts left by the finished task and clean up only the ones with proven ownership and explicit authorization.

Frequently Asked Questions about skill-disposable-artifact-cleanup

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

FAQPage Schema
How do I safely clean up temporary files after a workflow finishes?▼

Run an audit first to establish each artifact's exact path, producing task, and retention dependencies. Direct cleanup then requires explicit authorization and removes only the approved exact files or task-owned directories, never shared roots.

How to clean up Git worktrees left by a development task?▼

Git worktree cleanup is delegated, not performed directly. Route the worktree to the branch-finishing workflow after verified Git disposition, then use native cleanup or git worktree remove; never recursively delete the worktree directory.

Can I delete untracked files reported by Git during cleanup?▼

Untracked paths are review candidates only until producer ownership is proven. Filename similarity, age, or Git ignore status does not establish ownership, so uncertain paths must be preserved.

What files should never be deleted during artifact cleanup?▼

Preserve tracked and staged files, user data, credentials, environment files, databases, backups, uploads, normal profiles, and anything needed for active verification, debugging, recovery, or handoff. Nested repositories and unresolved symlinks are also protected.

Why is a cleanup candidate marked as blocked or preserved?▼

A candidate is preserved when ownership evidence is missing, stale, or uncertain, or when retention dependencies still exist. Recovery requires re-establishing exact identity, producer, owner, and cleanup authority through the current plan or a validated handoff.