Kill Dev Process

Classifies and safely kills orphaned dev servers/browsers with a hard exclusion list for databases and the IDE.

Tested · Works

Test report

Verdict
Tested · Works
Score
9.6/10
Tested
Jul 13, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Jul 18, 2026 · afb0fbb

Ran the actual step-1 investigation commands on a live dev machine: they surfaced postgres on :5432 and Claude's own IDE Helper node processes mixed in with real dev servers - exactly the kind of thing a naive 'kill everything matching node|chrome' baseline would have blindly nuked, which the skill's safety-check step explicitly excludes.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 5/5
  • Triggers reliably 5/5
  • Output vs. baseline 9/10
  • Docs & honesty 5/5

What Kill Dev Process does

Investigates listening ports and node/browser/build-tool processes, classifies them into Dev Servers / Browsers / Build Tools / Other in a table, explicitly excludes databases/Docker/SSH/the IDE itself, and only kills after user confirmation (graceful TERM then KILL). Trigger it when a port is occupied, too many node or Chrome processes have piled up, or you want a clean dev-environment slate; macOS-only (lsof/ps flags).

How to install Kill Dev Process

git clone https://github.com/nokonoko1203/claude-code-settings
cd claude-code-settings
mkdir -p ~/.claude/skills
cp -r skills/kill-dev-process ~/.claude/skills/kill-dev-process

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Kill Dev Process

  • /kill-dev-process Classifies and safely kills orphaned dev servers/browsers with a hard exclusion list for databases and the IDE.

It also activates on plain-language prompts like these:

  • Find and kill the orphaned dev servers hogging my ports
  • Clean up all these leftover node and Chrome processes safely
  • Free up port 3000 without killing my database or IDE

Frequently asked questions

Is the Kill Dev Process skill free?
Yes. The skill itself is free from nokonoko1203/claude-code-settings. SkillProof publishes the install command and an independent test verdict at no cost.
Does Kill Dev Process work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 13, 2026. Verdict: Tested · Works. Ran the actual step-1 investigation commands on a live dev machine: they surfaced postgres on :5432 and Claude's own IDE Helper node processes mixed in with real dev servers - exactly the kind of thing a naive 'kill everything matching node|chrome' baseline would have blindly nuked, which the skill's safety-check step explicitly excludes.
What is the Kill Dev Process SkillProof Score?
9.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 9/10, docs & honesty 5/5.
How do I install Kill Dev Process?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Kill Dev Process with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.