Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your project

AI-powered recommendations based on your stack.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

orphaned-process-cleanup | claude-utils

Home
Skills
claude-utils
orphaned-process-cleanup

Skill

orphaned-process-cleanup

From claude-utils

Find and clean up leaked browser, test-runner, and dev-server processes after interrupted sessions. Use when a task leaves Chromium, Playwright, Vitest, Jest, or long-lived dev servers behind.

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/claude-utils:orphaned-process-cleanup

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Use this skill when local development processes survived after the session that created them.

Supporting Files

agents/openai.yaml

SKILL.md

24 lines · ~248 tokens

Stats

Parent stars0

MaintenanceExcellent

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Parent stars0

MaintenanceExcellent

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Orphaned Process Cleanup

Use this skill when local development processes survived after the session that created them.

Workflow

Identify candidate processes owned by the current user.
Confirm they match the leaked-process patterns you are targeting.
Check elapsed runtime so you do not kill fresh processes that may still be in use.
Terminate only the stale processes that match the cleanup scope.
Re-check the process list and report what was removed.

Guardrails

Never kill processes owned by another user.
Never kill the current shell, parent shell, or obviously active sessions.
Prefer narrow process matching over broad pkill patterns.
Report the exact patterns you used and anything you left untouched.

$

npx claudepluginhub mariogusmao/mg-plugins --plugin claude-utils

Similar Skills

process-cleanup

13

Finds stale and resource-hungry processes, scores waste, and presents cleanup report. Activates on RAM queries or slow machine, or proactively when noticing sluggishness.

3 files1 tool

View process-cleanup

clean-machine

12

Audit and clean a developer's machine — dotfolders, caches, language toolchains, package globals — with per-target classification and risk surfacing. Produces cleanup records. Not for cleaning code or user files.

20 files4 tools

View clean-machine

prune-workflows

45

Interactively bulk-cancel stale non-terminal workflows with a dry-run preview, safeguard checks, and user confirmation before applying.

View prune-workflows