Guru Cleanup Task Resources

Name: Guru Cleanup Task Resources
Author: castbox

ASecurity

Remove only the current Finish-owned branch, worktree and runtime resources after terminal success.

8 stars

0 votes

0 copies

0 views

Added 9/20/2026

databasesreactgit

Works with

terminal

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add castbox/guru-trellis --skill guru-cleanup-task-resources --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Guru Cleanup Task Resources?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Guru Cleanup Task Resources

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/castbox-guru-cleanup-task-resources/badge)](https://www.skillsdirectory.com/skills/castbox-guru-cleanup-task-resources)

More formats (shields.io, HTML) on the badges page.

Download Zip

Files

SKILL.md

---
name: guru-cleanup-task-resources
description: Remove only the current Finish-owned branch, worktree and runtime resources after terminal success.
---

# Guru Cleanup Task Resources

Cleanup consumes one current Finish `success`. It shows the exact owned
resources, requires an independent confirmation when a deletion remains, and
preserves user checkouts, other task resources, archives and shared runtime
state. A fresh empty set or a reviewed set whose resources are already absent
is a normal `cleaned` terminal state.

The executor accepts only a complete terminal Finish transaction, an exact
clean registered worktree for that transaction's head branch, the merged local
head branch, `origin/<head_branch>`, its exact remote-tracking ref, and
task-bound runtime files. Existing Git refs must still point to the Finish
commit. It never force-removes a worktree or removes the checkout executing
Cleanup.

After successful deletion, Cleanup records one ignored-runtime terminal
receipt before retiring the Finish receipt. An exact same-input retry can
therefore recover `cleaned` after stdout loss. A pending `remaining_resources`
route emits only task/archive/Finish continuation identity and does not require
the Finish receipt to remain readable. The terminal receipt also binds the
Finish lifecycle generation, and Reactivate invalidates all prior Cleanup
receipts for the task.

Attribution

castbox

View source More from castbox →

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

--- name: guru-cleanup-task-resources description: Remove only the current Finish-owned branch, worktree and runtime resources after terminal success. --- # Guru Cleanup Task Resources Cleanup consumes one current Finish `success`. It shows the exact owned resources, requires an independent confirmation when a deletion remains, and preserves user checkouts, other task resources, archives and shared runtime state. A fresh empty set or a reviewed set whose resources are already absent is a normal `cleaned` terminal state. The executor accepts only a complete terminal Finish transaction, an exact clean registered worktree for that transaction's head branch, the merged local head branch, `origin/<head_branch>`, its exact remote-tracking ref, and task-bound runtime files. Existing Git refs must still point to the Finish commit. It never force-removes a worktree or removes the checkout executing Cleanup. After successful deletion, Cleanup records one ignored-runtime terminal receipt before retiring the Finish receipt. An exact same-input retry can therefore recover `cleaned` after stdout loss. A pending `remaining_resources` route emits only task/archive/Finish continuation identity and does not require the Finish receipt to remain readable. The terminal receipt also binds the Finish lifecycle generation, and Reactivate invalidates all prior Cleanup receipts for the task.