kill-dev-process

Dev Environment Cleanup

Safely clean up processes accumulated during development (dev servers, browsers, node, etc.).

Usage: /kill-dev-process Usage: /kill-dev-process $MODE

$ARGUMENTS to specify mode:

• ports — Only processes occupying listening ports
• browsers — Only browser processes
• all — Process all categories at once
• No argument — Interactive selection

Execution Steps

Step 1: Investigate the Current State

Run the following commands in parallel to assess the current situation:

# List listening TCP ports (macOS)
lsof -iTCP -sTCP:LISTEN -P -n 2>/dev/null | grep -v "^COMMAND"

# Dev-related node processes
ps aux | grep -E '[n]ode|[t]sx|[v]ite|[n]ext|[n]uxt|[e]sbuild|[t]sc |[b]un ' | grep -v 'grep'

# Browser processes (including those from Playwright/Chrome DevTools MCP)
ps aux | grep -E '[C]hromium|[c]hrome|[C]hrome Helper|[p]laywright' | grep -v 'grep'

Step 2: Classify and Display Results

Classify detected processes into the following categories and display in table format:

Category	Criteria
Dev Servers	Processes listening on ports 3000-9999 via node/bun/deno
Browsers	Chromium, Chrome, Playwright-related processes
Build Tools	Residual esbuild, tsc, webpack, turbopack, etc.
Other	Anything else requiring user confirmation

Display format example:

## Detected Processes

### Dev Servers (3 items)
PID    PORT   COMMAND              STARTED
12345  3000   node next-server     10:30
12346  5173   node vite            11:45
12347  8080   node express         09:00

### Browsers (5 items)
PID    COMMAND                      MEM
23456  Chromium --headless           120M
23457  Chrome Helper (Renderer)       80M
...

Step 3: Safety Check

Processes that must NEVER be killed:

• System processes (PID < 100, root-owned system daemons)
• Databases (postgres, mysql, redis, mongo)
• Docker / containerd
• SSH / sshd
• IDE itself (VSCode, Cursor) — Chrome helpers ARE eligible targets
• Long-running processes that appear to be intentionally started by the user