Individual skill

go-cli-testing

Design, implement, stabilize, and review Go CLI tests across fresh command trees, pure logic, table-driven cases, streams, typed configuration, files, environment, function-backed HTTP fakes, repositories, subprocesses, capability profiles, race checks, and artifact behavior. Use when adding command tests, diagnosing flaky Go tests, choosing test boundaries, or verifying human-, agent-, and CI-facing CLI contracts.

plugins/LVTD-LLC/skills/skills/go-cli-testing/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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,532
Repository last updated
Nov 6, 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 Testing

Test observable behavior at the narrowest boundary that proves it. Isolate every
mutable resource and reserve executable tests for process-level semantics.

## Core Workflow

1. Inventory success, invalid, boundary, dependency-failure, and cancellation behavior.
2. Map each case to a pure, command, adapter, integration, or binary test.
3. Inject arguments, streams, configuration, clocks, and effectful dependencies.
4. Isolate files, environment, servers, repositories, ports, and subprocesses.
5. Assert stdout, stderr, exit behavior, and errors according to the public contract.
6. Gate live or platform-specific tests and make their changes reversible.
7. Run standard, race, tagged, and relevant platform checks.