killing-processes — community killing-processes, grokking-concurrency-exercise, community, ide skills

v1.0.0

About this Skill

Perfect for Development Agents needing to manage multiple Node.js projects and ports simultaneously. 開発サーバーや Node.js プロセスを強制終了。ポート競合の解決やプロセスリセット時に使用。

k2works k2works
[0]
[0]
Updated: 2/28/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
43
Canonical Locale
ja
Detected Body Locale
ja

Perfect for Development Agents needing to manage multiple Node.js projects and ports simultaneously. 開発サーバーや Node.js プロセスを強制終了。ポート競合の解決やプロセスリセット時に使用。

Core Value

Empowers agents to forcefully terminate development processes, including Node.js servers, freeing up ports and resources using options like --port and --check, ensuring efficient project switching and resource allocation.

Ideal Agent Persona

Perfect for Development Agents needing to manage multiple Node.js projects and ports simultaneously.

Capabilities Granted for killing-processes

Automating development process termination for multiple projects
Debugging port conflicts by forcefully stopping specific Node.js processes
Optimizing resource usage by bulk terminating unused development servers

! Prerequisites & Limits

  • Requires command-line interface access
  • Limited to Node.js development processes
  • May require administrative privileges for process termination

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is killing-processes?

Perfect for Development Agents needing to manage multiple Node.js projects and ports simultaneously. 開発サーバーや Node.js プロセスを強制終了。ポート競合の解決やプロセスリセット時に使用。

How do I install killing-processes?

Run the command: npx killer-skills add k2works/grokking-concurrency-exercise/killing-processes. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for killing-processes?

Key use cases include: Automating development process termination for multiple projects, Debugging port conflicts by forcefully stopping specific Node.js processes, Optimizing resource usage by bulk terminating unused development servers.

Which IDEs are compatible with killing-processes?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for killing-processes?

Requires command-line interface access. Limited to Node.js development processes. May require administrative privileges for process termination.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add k2works/grokking-concurrency-exercise/killing-processes. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use killing-processes immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

killing-processes

Install killing-processes, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Kill Development Processes

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

Instructions

1. オプション

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

2. 基本例

bash
1# 全開発プロセスを強制終了 2# 「すべての Node.js 開発サーバー(npm run dev 等)を停止」 3 4# ポート 3000 番のプロセスのみ終了 5# --port 3000 6# 「ポート 3000 で動作中のプロセスを終了」 7 8# プロセス状況の確認 9# --check 10# 「現在起動中の開発プロセスを一覧表示」

3. 詳細機能

一括プロセス終了

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

bash
1# ポート範囲でのプロセス検索・終了 2netstat -ano | findstr ":300[0-9]" | findstr LISTENING 3taskkill //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. 連携シナリオ

bash
1# 開発中のエラー修正後にプロセスリセット 2npm run dev 3# 「エラーが発生」→ kill → 「全プロセス停止して再起動準備」 4 5# ポート競合の解決 6npm start 7# 「Port 3000 is already in use」→ kill --port 3000 8 9# 開発環境のクリーンアップ 10git checkout main 11# → kill → 「ブランチ切り替え前に開発プロセスをクリーンアップ」

6. 注意事項

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

7. ベストプラクティス

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

Related Skills

Looking for an alternative to killing-processes or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer