foryourhealth111-pixel/node-zombie-guardian
Use when diagnosing stale or orphaned Node.js processes launched by VCO, auditing ownership/liveness, or safely simulating cleanup without touching external Node workloads.
npx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill node-zombie-guardian
This skill is for managed-process hygiene inside the VCO ecosystem.
It exists to answer one question safely: which Node processes belong to VCO, which of them are stale, and which of those are eligible for cleanup without risking live external workloads.
ownership = vco-managed can ever become cleanup candidates.external and unknown processes remain audit-only.-Apply mode remains simulation-only and must never terminate real processes.This skill is a focused wrapper around the operator scripts that live in the bundled vibe skill:
../vibe/scripts/common/NodeLaunchWrapper.ps1../vibe/scripts/governance/Invoke-NodeProcessAudit.ps1../vibe/scripts/governance/Invoke-NodeZombieCleanup.ps1../vibe/scripts/verify/vibe-node-zombie-gate.ps1Use the wrapper when VCO starts a Node workload that should be tracked in the ledger.
& "..\vibe\scripts\common\NodeLaunchWrapper.ps1" `
-RepoRoot "C:\path\to\repo" `
-Command "node" `
-ArgumentList @("scripts\worker.js")
Default mode is read-only and emits a report.
& "..\vibe\scripts\governance\Invoke-NodeProcessAudit.ps1" `
-RepoRoot "C:\path\to\repo" `
-WriteArtifacts
Expected outcomes:
managed_live, managed_stale, external_audit_onlyCleanup remains report-only unless explicitly switched, and the safety filters still apply.
& "..\vibe\scripts\governance\Invoke-NodeZombieCleanup.ps1" `
-RepoRoot "C:\path\to\repo" `
-WriteArtifacts
Use this to confirm which managed stale processes would be targeted before any real cleanup path is considered.
Run the dedicated gate before trusting changes in this area:
& "..\vibe\scripts\verify\vibe-node-zombie-gate.ps1" -WriteArtifacts
The gate proves:
-Apply mode stays simulatedTake foryourhealth111-pixel/node-zombie-guardian from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.