Individual skill

go-cli-process-control

Execute and supervise external programs safely from Go CLIs with explicit arguments, typed failure classification, working directories, environments, bounded streams, deadlock-safe pipes, contexts, timeouts, signals, platform adapters, descendant cleanup, runner seams, and lifecycle tests. Use when wrapping a command, diagnosing start or exit failures, hangs, deadlocks, or orphan processes, or implementing cancellable cross-platform CLI workflows.

plugins/LVTD-LLC/skills/skills/go-cli-process-control/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,538
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Go CLI Process Control

Treat child-process lifecycle as correctness. Observe the terminal result,
propagate cancellation, and clean up every process, pipe, and temporary resource.

## Core Workflow

1. Define the child executable, argv, environment, directory, streams, and success contract.
2. Use an explicit shell only when shell semantics are actually required.
3. Inject a runner boundary and propagate the caller's context.
4. Observe startup and completion; preserve status and useful redacted stderr.
5. Bound captured output, cancellation, and shutdown time.
6. Account for descendants and wait for every pipeline stage.
7. Test missing tools, bad exits, malformed output, cancellation, signals, and cleanup.