kill
Skill2 starsChanged 5 days agoMITView on GitHub
Kill all dev processes running on this machine (dev servers, watchers, bundlers) without touching the active Claude Code session.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- RemiPelloux/kill-my-ideatheir own version, first seen Nov 15, 2026
- mikerugg/skillstheir own version, first seen Oct 6, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- RemiPelloux/kill-my-idea★ 2same name
- mikerugg/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- 1passwordSkill
- brainSkill
- brainstormSkill
- bridgeSkill
- claude-switcherSkill
- clear-cacheSkill
- commitSkill
- cross-artifactSkill
- ctoSkill
- diskSkill
- lookSkill
- parseSkill
- pbarSkill
- planSkill
- pruneSkill
- pushSkill
- reportSkill
- researchSkill
- swarmSkill
- vibe-auditSkill
- video-editorSkill
- webSkill
- wikiSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Every key is optional, and the whole file is optional — with no kit.json, or a kit.json lacking a kill key, the built-in defaults below …
- Very specific: line 117
If .claude/kit.json has a rules."kill" entry, read it and apply it as an additional instruction for this skill.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kill Dev Processes
Finds and kills all development processes — dev servers, file watchers, bundler instances, etc. Leaves the active Claude Code session untouched.
Configuration
Ports and extra process patterns come from .claude/kit.json when present:
{
"kill": {
"ports": [3000, 3001, 5173, 8787],
"portRanges": [[9615, 9634]],
"patterns": ["my-custom-watcher"],
"scopeToProjectPath": true
}
}Every key is optional, and the whole file is optional — with no kit.json, or a kit.json
lacking a kill key, the built-in defaults below apply. scopeToProjectPath additionally kills
node/tsx processes whose command line contains this project's path, for repos that run dev servers
on shared ports.
Procedure
- Find and kill processes listening on dev ports:
PORTS=$(jq -r '((.kill.ports // [])[]), ((.kill.portRanges // [])[] | range(.[0]; .[1]+1))' .claude/kit.json 2>/dev/null)
[ -z "$PORTS" ] && PORTS=$(printf '%s\n' 3000 3001 4000 4444 5173 5174 8080 8787 8788 8789; seq 9615 9634)
echo "$PORTS" | while IFS= read -r port; do
[ -z "$port" ] && continue
pids=$(lsof -iTCP:$port -sTCP:LISTEN -t 2>/dev/null)
if [ -n "$pids" ]; then
echo "Killing port $port: PIDs $pids"
echo "$pids" | xargs kill 2>/dev/null
fi
doneThe shell is zsh. It does not word-split unquoted parameter expansions, so
for port in $PORTSwould pass the entire list as a single argument and silently match nothing. Always iterate withecho "$VAR" | while IFS= read -r. This applies to everykit.jsonarray.
- Find and kill common dev tool processes:
pgrep -f "wrangler dev" 2>/dev/null | xargs kill 2>/dev/null
pgrep -f "tsx watch" 2>/dev/null | xargs kill 2>/dev/null
pgrep -f "next dev" 2>/dev/null | xargs kill 2>/dev/null
pgrep -f "vite" 2>/dev/null | xargs kill 2>/dev/null
pgrep -f "nodemon" 2>/dev/null | xargs kill 2>/dev/null
# Project-specific patterns from kit.json
jq -r '(.kill.patterns // [])[]' .claude/kit.json 2>/dev/null | while IFS= read -r pat; do
[ -z "$pat" ] && continue
pgrep -f "$pat" 2>/dev/null | xargs kill 2>/dev/null
done
# Processes scoped to this project's path, when kit.json opts in
if [ "$(jq -r '.kill.scopeToProjectPath // false' .claude/kit.json 2>/dev/null)" = "true" ]; then
pgrep -f "node.*$(pwd).*dev" 2>/dev/null | xargs kill 2>/dev/null
pgrep -f "tsx watch.*$(pwd)" 2>/dev/null | xargs kill 2>/dev/null
fi- Find and kill Puppeteer, Chrome debug, artifact bridge, and clean registry:
# Kill all puppeteer server processes
pgrep -f "puppeteer-server" 2>/dev/null | xargs kill 2>/dev/null
pgrep -f "chrome.*claude-chrome" 2>/dev/null | xargs kill 2>/dev/null
pgrep -f "artifact-bridge" 2>/dev/null | xargs kill 2>/dev/null
# Clear the chrome registry since we killed everything
echo '[]' > ~/.claude-chrome-registry.json 2>/dev/null- Verify nothing is left on dev ports:
echo "$PORTS" | while IFS= read -r port; do
[ -z "$port" ] && continue
pid=$(lsof -iTCP:$port -sTCP:LISTEN -t 2>/dev/null)
if [ -n "$pid" ]; then
echo "WARNING: port $port still occupied by PID $pid"
fi
done
echo "Done."$PORTS is still in scope from step 1. If running step 4 standalone, rebuild it with the same
two lines.
- Report what was killed (ports freed, process names). If nothing was running, say so.
Rules
- No confirmation needed — execute immediately
- Never kill Claude Code — do not touch processes matching
claude,claude-code, or the current shell's ancestor PIDs - Never kill non-dev processes — only target processes related to dev servers and tools
- SIGTERM first — use
kill, notkill -9. Only escalate tokill -9if a process survives after 2 seconds - Exit codes 143/137 from killed background tasks are expected — ignore them
Project overrides
If .claude/kit.json has a rules."kill" entry, read it and apply it as an additional
instruction for this skill. Absent file or key means no overrides — that is the normal case.
jq -r '.rules."kill" // empty' .claude/kit.json 2>/dev/nullDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

