Kill Development Processes

VerifiedCaution

Kills Node.js development processes on Windows. Supports killing all processes, a specific port, or just listing active processes.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#process-management#nodejs#windows#port-killing

Recommended for

Automated summary

Stops all or specific development processes (e.g., Node.js servers) running on specified ports, commonly used to resolve port conflicts or reset environments.

Strengths

  • Kills all Node.js development processes in one command
  • Supports targeting specific ports for precision
  • Provides a check-only mode to list processes before killing

Limitations

  • Designed for Windows (uses taskkill); not cross-platform by default
  • May require administrator privileges for some processes
  • Cannot handle non-Node.js processes unless explicitly specified
When to use it

When you encounter port-in-use errors or need to quickly clean up all development servers before switching branches or restarting.

When not to use it

When you need to gracefully shut down servers (e.g., saving state) or when processes belong to critical production services.

Security analysis

Caution
Quality score88/100

The skill uses forceful process termination via taskkill /F, which can disrupt unsaved work. While it does not perform any destructive or exfiltrating actions, the ability to kill processes is a powerful operation that warrants caution to avoid unintended data loss.

Findings
  • •Uses taskkill /F to forcefully terminate processes, which can cause data loss if unsaved work exists.
  • •Relies on Windows-specific commands (taskkill, netstat) and will not work on other operating systems.
How this analysis is made

Examples

Kill all Node.js dev processes
Kill all Node.js development servers running on any port.
Kill process on specific port
Kill the process running on port 3000.
Check running processes
Check which development processes are currently running without killing them.

name: killing-processes description: 開発サーバーや Node.js プロセスを強制終了。ポート競合の解決やプロセスリセット時に使用。

Kill Development Processes

開発サーバーや Node.js プロセスを強制終了するスキル。複数ポートで起動している開発プロセスを一括で停止できます。

Instructions

1. オプション

  • なし : すべての Node.js 開発プロセスを強制終了
  • --port <ポート番号> : 特定のポートのプロセスのみ終了
  • --check : プロセス状況の確認のみ(終了せず)

2. 基本例

# 全開発プロセスを強制終了
# 「すべての Node.js 開発サーバー(npm run dev 等)を停止」

# ポート 3000 番のプロセスのみ終了
# --port 3000
# 「ポート 3000 で動作中のプロセスを終了」

# プロセス状況の確認
# --check
# 「現在起動中の開発プロセスを一覧表示」

3. 詳細機能

一括プロセス終了

Windows 環境で複数の開発サーバーが起動している場合の一括終了処理。

# ポート範囲でのプロセス検索・終了
netstat -ano | findstr ":300[0-9]" | findstr LISTENING
taskkill //F //PID <PID1> && taskkill //F //PID <PID2>

個別ポート指定終了

特定のポートで起動しているプロセスのみを終了する。

  • 安全性: 指定ポートのみ終了で他に影響しない
  • 精密性: 必要最小限のプロセス停止
  • 確認: 終了前にプロセス情報を表示

4. 出力例

現在起動中の開発プロセス:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ポート 3000: PID 34348 (Node.js)
ポート 3001: PID 16676 (Node.js)
ポート 3002: PID 25696 (Node.js)

プロセス終了中...
PID 34348 を終了しました
PID 16676 を終了しました
PID 25696 を終了しました

すべての開発プロセスを停止しました。

5. 連携シナリオ

# 開発中のエラー修正後にプロセスリセット
npm run dev
# 「エラーが発生」→ kill → 「全プロセス停止して再起動準備」

# ポート競合の解決
npm start
# 「Port 3000 is already in use」→ kill --port 3000

# 開発環境のクリーンアップ
git checkout main
# → kill → 「ブランチ切り替え前に開発プロセスをクリーンアップ」

6. 注意事項

  • 前提条件: Windows 環境(taskkill コマンド使用)
  • 制限事項: 管理者権限が必要な場合があります
  • 推奨事項: 重要な作業中は事前にファイル保存を行う

7. ベストプラクティス

  1. 安全な終了: 作業中のファイルは事前に保存する
  2. 段階的終了: まず --check で状況確認してから終了
  3. ポート指定: 必要に応じて特定ポートのみ終了
  4. 再起動準備: プロセス終了後は適切にサーバーを再起動

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/kill-development-processes-mm5t8cgm/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/kill-development-processes-mm5t8cgm' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/kill-development-processes-mm5t8cgm/download' --output '.skill-downloads/kill-development-processes-mm5t8cgm/SKILL.md.part' && mv '.skill-downloads/kill-development-processes-mm5t8cgm/SKILL.md.part' '.skill-downloads/kill-development-processes-mm5t8cgm/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/kill-development-processes-mm5t8cgm/SKILL.md' && test -s '.skill-downloads/kill-development-processes-mm5t8cgm/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/killing-processes' && cp -R '.skill-downloads/kill-development-processes-mm5t8cgm' '.claude/skills/killing-processes'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/kill-development-processes-mm5t8cgm'

openskills read 'kill-development-processes-mm5t8cgm'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/kill-development-processes-mm5t8cgm/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills