hung-run-recovery

Terminate hung command sessions and re-run scripts with timeout budgets.

7|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sparkeh9/DoclingDotNet --skill hung-run-recovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hung-run-recovery
Source: https://github.com/sparkeh9/DoclingDotNet/tree/main/.agent/skills/hung-run-recovery
Command: npx skills add https://github.com/sparkeh9/DoclingDotNet --skill hung-run-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recover from hung command sessions by targeted process discovery and safe termination, with anti-hang guards to keep workflows moving.

Core Features & Use Cases

  • Detect hung processes with no output within a defined window and stalled sessions.
  • Locate and terminate only processes matching the original command intent (no blanket kills).
  • Re-run tasks with safeguards: timeout budgets, output heartbeat, and scoped restarts.

Quick Start

Identify the hung process, terminate the matching one, then re-run the command with an explicit timeout.

Frequently Asked Questions about hung-run-recovery

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

FAQPage Schema
How do I safely terminate a hung shell script without killing unrelated processes?

To terminate hung shell scripts safely, this Skill uses targeted process discovery by command line to locate and terminate only processes matching the original command intent, avoiding blanket kills and preventing unrelated process termination.

What is the best way to recover from stalled long-running services that have no output?

Recovering from stalled long-running services involves detecting hung processes with no output within a defined window, terminating the matching process safely, then re-running the task with timeout budgets and heartbeat signals.

How do I clean up orphaned child processes that linger after a script exits?

Cleaning up orphaned child processes requires identifying the lingering processes by their command line arguments and applying safe termination procedures scoped to the original command intent to restore workflow progress.

Can I re-run a stalled command with safeguards to prevent it from hanging again?

You can re-run stalled commands with safeguards by applying explicit timeout budgets, output heartbeat monitoring, and scoped restarts to ensure the workflow continues moving and prevents future process hangs.

Does this process recovery method work for long-running shell scripts?

This process recovery method works specifically for long-running shell scripts or services that stall without output, applying targeted discovery and safe termination to restore workflow progress.