delete-shared-runtime

Safely removes or archives shared runtime checkouts after verifying references, git state, and running processes.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill delete-shared-runtime-ryokuman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delete-shared-runtime
Source: https://github.com/Ryokuman/new_human_ochestrator/tree/main/system/20-skills/delete-shared-runtime
Command: npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill delete-shared-runtime-ryokuman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deleting a shared runtime checkout that multiple task silos still reference can break open PRs, running servers, and unpushed work. This Skill enforces a safe deletion workflow that checks references, git state, and active processes before removing or archiving runtime directories. ## Core Features & Use Cases - Reference Verification: Scans runtime registry/status, task silo goals, open PRs, handoffs, running processes, and ports before any deletion. - Archive-First Policy: Marks runtimes as status: archived with reason and date when deletion is uncertain, instead of removing them outright. - Guarded Destructive Actions: Only deletes directories after explicit user approval, blocking removal when dirty state, ahead commits, or active references exist. - Use Case: When cleaning up an old shared-runtime/<project-id>/<runtime-name>/ checkout, the Skill checks linked tasks and git status, reports preservation risks, and archives or deletes only after confirmation. ## Quick Start Ask the agent to review and safely delete or archive the shared runtime named api-server for project demo, checking all references first.

Frequently Asked Questions about delete-shared-runtime

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

FAQPage Schema
How do I safely delete a shared runtime checkout used by multiple tasks?

Check the runtime registry for linked_tasks, scan open task silo goals and PRs for references, verify no running processes or ports are in use, and confirm the git checkout is clean with no unpushed commits. Only delete after explicit approval; otherwise mark it archived.

What checks should run before removing a git worktree or runtime directory?

Run git status --short --branch to detect dirty state and ahead commits, search the repo for path references with ripgrep, and check ports with lsof. If any reference, process, or uncommitted change exists, preserve the directory instead of deleting it.

When should a runtime be archived instead of deleted?

Archive when deletion is uncertain, references might still exist, or the removal scope is not explicitly approved. Set status to archived with archived_at date and archive_reason in the registry, keeping the directory intact until deletion is confirmed safe.

Can a runtime connected to an open PR be deleted?

No. The Skill explicitly forbids deleting runtime checkouts linked to open PR heads or branches under review. These must be preserved until the PR is merged or closed and references are cleared.

What are the limitations of automated runtime cleanup?

Automated cleanup cannot judge business context, so destructive deletion always requires explicit user approval or a pre-approved work scope. Secret values are never read as deletion criteria, and project-specific runtime configs are not copied into the shared system layer.