Run any Skill in Manus with one click

terminate-stuck-test-executables

Stars26

Forks3

UpdatedMay 25, 2026 at 22:02

Safely terminate stuck test executables that block rebuilds or CTest runs on Windows. Use when a test binary is locked or still running, or when the user says a test executable is stuck, hung, blocking the linker, or needs to be killed. Read the executable list from the generated CTest config and always ask the user for permission before use.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jbalcomb

jbalcomb/ReMoM

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	terminate-stuck-test-executables
description	Safely terminate stuck test executables that block rebuilds or CTest runs on Windows. Use when a test binary is locked or still running, or when the user says a test executable is stuck, hung, blocking the linker, or needs to be killed. Read the executable list from the generated CTest config and always ask the user for permission before use.

Terminate Stuck Test Executables

Use this skill when a Windows test executable is still running and blocking a rebuild, test discovery, or CTest execution.

Safety Rules

Ask the user for permission immediately before using this skill.
Only target executables discovered from the generated CTest config unless the user explicitly approves a wider action.
Prefer listing candidate processes first when the environment allows it.
After termination, rerun the narrowest blocked validation step.

Executable Source

The helper reads executables from generated CTest files such as:

out/build/<preset>/CTestTestfile.cmake
out/build/<preset>/**/*_tests.cmake

Script Asset

Use the bundled script:

./kill-stuck-test-processes.py

Suggested Invocation

Python example:

python .\.claude\skills\terminate-stuck-test-executables\kill-stuck-test-processes.py --build-dir .\out\build\MSVC-release --name MOM_tests.exe

List discovered test executables without killing anything:

python .\.claude\skills\terminate-stuck-test-executables\kill-stuck-test-processes.py --build-dir .\out\build\MSVC-release --list

Kill every currently running executable discovered from that CTest config:

python .\.claude\skills\terminate-stuck-test-executables\kill-stuck-test-processes.py --build-dir .\out\build\MSVC-release --all

Response Pattern

Before use, say:

I found a stuck test executable. I can terminate it with the terminate-stuck-test-executables skill and then rerun the blocked validation. Please confirm if you want me to use it.

After use, report:

which processes were terminated
which names were not running
which names were discovered from CTest
which validation step was rerun

More from this repository

same repository

vet-dependency

jbalcomb/ReMoM

Vet a third-party dependency before recommending, installing, or adding it. Use whenever a new external binary, library, package, or tool is proposed - including anything installed via winget/choco/vcpkg/FetchContent, any DLL committed to the repo, and any tool suggested to the user. Also use when the user challenges a dependency's pedigree, provenance, trustworthiness, or supply-chain risk.

2026-07-2226

prd-to-plan

jbalcomb/ReMoM

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in doc/#AI_Plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

2026-07-1526

name	terminate-stuck-test-executables
description	Safely terminate stuck test executables that block rebuilds or CTest runs on Windows. Use when a test binary is locked or still running, or when the user says a test executable is stuck, hung, blocking the linker, or needs to be killed. Read the executable list from the generated CTest config and always ask the user for permission before use.

Terminate Stuck Test Executables

Use this skill when a Windows test executable is still running and blocking a rebuild, test discovery, or CTest execution.

Safety Rules

Ask the user for permission immediately before using this skill.
Only target executables discovered from the generated CTest config unless the user explicitly approves a wider action.
Prefer listing candidate processes first when the environment allows it.
After termination, rerun the narrowest blocked validation step.

Executable Source

The helper reads executables from generated CTest files such as:

out/build/<preset>/CTestTestfile.cmake
out/build/<preset>/**/*_tests.cmake

Script Asset

Use the bundled script:

./kill-stuck-test-processes.py

Suggested Invocation

Python example:

python .\.claude\skills\terminate-stuck-test-executables\kill-stuck-test-processes.py --build-dir .\out\build\MSVC-release --name MOM_tests.exe

List discovered test executables without killing anything:

python .\.claude\skills\terminate-stuck-test-executables\kill-stuck-test-processes.py --build-dir .\out\build\MSVC-release --list

Kill every currently running executable discovered from that CTest config:

python .\.claude\skills\terminate-stuck-test-executables\kill-stuck-test-processes.py --build-dir .\out\build\MSVC-release --all

Response Pattern

Before use, say:

I found a stuck test executable. I can terminate it with the terminate-stuck-test-executables skill and then rerun the blocked validation. Please confirm if you want me to use it.

After use, report:

which processes were terminated
which names were not running
which names were discovered from CTest
which validation step was rerun