skills.rest
OpenRouterTeam
OpenRouterTeamOFFICIAL
Explore all skills by this author →
Website𝕏@openrouterGitHub

kill-port

Clear occupied local dev service ports and recover stuck Tilt development stacks.

7|12|Updated Mar 26, 2026
Search Tags:#process management#dev environment#bun#local development#tilt#port cleanup#kill-port
One-click install
npx skills add https://github.com/OpenRouterTeam/docs --skill kill-port-openrouterteam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kill-port
Source: https://github.com/OpenRouterTeam/docs/tree/main/.agents/skills/kill-port
Command: npx skills add https://github.com/OpenRouterTeam/docs --skill kill-port-openrouterteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Local development services and Tilt stacks can leave lingering port listeners and stuck processes that block restarts, forcing developers to manually hunt down and kill processes before they can get their environment running again. ## Core Features & Use Cases - Port Cleanup: Run bun run kill-ports to clear lingering listeners on configured service ports, with --list to preview what will be killed. - Stuck Stack Recovery: Follow a guided sequence of stopping Tilt, running tilt down, clearing ports, and restarting with bun run dev:up. - Aggressive Cleanup: Use bun run kill-all to additionally stop the Tilt listener and matching wrangler, workerd, esbuild, and dev-server processes scoped to the repository. - Use Case: After a crashed dev session leaves port 3000 occupied, preview the listeners with bun run kill-ports --list, clear them, and restart the full stack cleanly. ## Quick Start Ask the assistant to clear the occupied dev service ports and restart the stuck Tilt stack using the repository cleanup commands.

Frequently Asked Questions about kill-port

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

FAQPage Schema
How do I kill a process occupying a local dev port?▼

Run `bun run kill-ports` to clear lingering listeners on the configured service ports. Use `bun run kill-ports --list` first to preview which listeners will be terminated before killing them.

How do I restart a stuck Tilt development stack?▼

Stop the Tilt process with Ctrl+C or SIGTERM, run `tilt down` to delete Tilt-managed resources, then run `bun run kill-ports` and restart with `bun run dev:up`. Note that `tilt down` does not stop the Tilt process itself.

What is the difference between kill-ports and kill-all?▼

kill-ports only clears listeners on configured service ports. kill-all additionally stops the Tilt listener and matching wrangler, workerd, esbuild, and dev-server processes, but only those under the repository path.

Does kill-ports stop Docker containers or Postgres?▼

No. The cleanup commands exclude Tilt and Docker containers entirely. Local Postgres is managed separately with `bun run db:stop`.

Why does tilt wait show Ready right after triggering a rebuild?▼

A `tilt wait` immediately after `tilt trigger <resource>` can observe the previous Ready state before the new build starts. Watch the new build and readiness in the Tilt UI instead of relying on an immediate wait.

Related Skills

Explore More Software Engineering Skills→
BlocUnited-LLCBlocUnited-LLC
14

setup

Set up a Mozaiks development environment with dependencies and environment variables.

Official
Intermediate
rcarmorcarmo
816

reload

Reinstalls piclaw from workspace source code and restarts the running process via Supervisor/systemd-Backspace or manual fallback.

Community
Intermediate
awfixers-stuffawfixers-stuff

zmx

Manage long-lived dev processes with consistent session prefixes and lifecycle controls.

Official
Intermediate
baasith6baasith6

detecting-port-conflicts

Diagnose port conflicts by identifying processes using lsof and offering resolution options.

Community
Intermediate