test_server_management_windows

Identify and terminate Windows processes occupying a specified network port.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/tim72117/word --skill test-server-management-windows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test_server_management_windows
Source: https://github.com/tim72117/word/tree/main/.agent/skills/test_server_management/windows
Command: npx skills add https://github.com/tim72117/word --skill test-server-management-windows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Windows port usage on Windows environments can block testing servers; this Skill helps identify and terminate the process occupying a port so tests can proceed.

Core Features & Use Cases

  • Identify and locate ports that are currently in use on Windows, including the PID.
  • Terminate blocking processes to free the port for immediate reuse in development or CI pipelines.
  • Use Case: When a build or test run fails due to a port conflict, this Skill quickly frees the required port.

Quick Start

Identify the PID occupying the target port with netstat and findstr, then terminate it with taskkill using that PID.

Frequently Asked Questions about test_server_management_windows

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

FAQPage Schema
How do I free a blocked network port on a Windows server?

Identify the blocking process PID by running netstat -ano with findstr, then terminate the process using taskkill to free the network port for reuse in local development or CI pipelines.

What is the best way to terminate a process occupying a port in Windows?

The best way to terminate a process occupying a port is using netstat -ano with findstr to locate the PID, then executing taskkill to stop the stuck process and resolve the port conflict.

Does this Windows port termination method work in Git Bash environments?

Yes, this port termination method works in Git Bash environments, providing specific command escaping guidance to correctly execute netstat -ano and taskkill for resolving port conflicts.

How do I find the PID of a process blocking a specific port on Windows?

Find the PID of a blocking process on Windows by running netstat -ano with findstr to filter the target port number, then use that PID with taskkill to terminate the process and free the port.

Can I use taskkill to stop a process blocking a port in a CI pipeline?

Yes, you can use taskkill to stop a process blocking a port in a CI pipeline by first identifying the PID with netstat -ano and findstr, allowing the automated test or build run to proceed immediately.