cleanup-zombies

Detect and kill zombie dev server and test processes on project ports.

8|2|Updated Oct 27, 2025

Search Tags:#testing #development #monorepo #port #process #kill

Ready to run

npx skills add https://github.com/ArcadeAI/safeword --skill cleanup-zombies

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup-zombies
Source: https://github.com/ArcadeAI/safeword/tree/main/.claude/skills/cleanup-zombies
Command: npx skills add https://github.com/ArcadeAI/safeword --skill cleanup-zombies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents lingering processes and port conflicts by killing zombie dev servers, test runners, and browser instances, ensuring smooth development and testing workflows.

Core Features & Use Cases

Auto-detection of project environment: Finds relevant ports from configuration files across monorepo structures.
Process termination: Kills processes associated with dev servers, browsers, and test runners based on port and process type.
Use Case: When a developer encounters a port in use or hung test processes, this Skill safely clears those processes specific to the current project to resume work efficiently.

Quick Start

Run the cleanup script with --dry-run to preview targets, then execute without the flag to terminate identified processes.

Frequently Asked Questions about cleanup-zombies

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

FAQPage Schema

How do I kill hung development server processes and free up ports?▼

To kill hung development server processes and free ports, run the cleanup script with a dry-run to preview targets, then execute it to safely terminate zombie processes associated with your current project.

How can I resolve port conflicts in a monorepo without killing unrelated processes?▼

To resolve port conflicts in a monorepo safely, the script auto-detects project environments by reading configuration files, ensuring it only terminates dev servers and test runners scoped to your current project.

How do I manually specify a port to terminate a lingering testing tool process?▼

You can manually override auto-detection by providing specific port numbers to the cleanup script, forcing targeted process termination for lingering testing tools that are not automatically found in configuration files.

How do I preview which zombie processes will be terminated before making changes?▼

To preview which zombie processes will be terminated, run the cleanup script using the dry-run flag to see a list of identified targets and their associated ports before executing actual process termination.

Why does my testing workflow leave hung processes and how can I clear them?▼

Testing workflows often leave hung processes from browser instances and test runners, which you can clear by running the cleanup script to terminate these specific zombie processes and prevent port conflicts.

Can I clear hung test runners and browser instances in multi-project environments?▼

Yes, you can clear hung test runners and browser instances in multi-project environments by running the cleanup script, which identifies and kills zombie processes related to your specific development and testing tools.