skills.rest
krzemienski
krzemienskiCOMMUNITY
Explore all skills by this author →
Website𝕏@nkrzemienskiGitHub

cli-validation

Validate CLI binaries and capture stdout, stderr, and exit codes.

2|Updated Apr 8, 2026
Search Tags:#cli#e2e-testing#stdin#json-csv#exit-codes#stdout-stderr#binary-validation
One-click install
npx skills add https://github.com/krzemienski/validationforge --skill cli-validation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-validation
Source: https://github.com/krzemienski/validationforge/tree/main/skill-audit-workspace/cli-validation/skill-snapshot
Command: npx skills add https://github.com/krzemienski/validationforge --skill cli-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, evidence-first workflow to verify that command-line tools build or install correctly and behave as expected across help/version output, happy-path execution, error cases, stdin/pipe handling, output formats, and exit codes.

Core Features & Use Cases

  • Cross-language build checks: Guidance for building or installing binaries for Rust, Go, Node.js, and Python projects and verifying the produced executable.
  • Behavioral validation: Exercises help and version flags, happy-path commands, invalid flags, missing arguments, file-not-found and permission error cases, and stdin/pipe behavior while recording stdout, stderr, and exit codes.
  • Output and evidence: Validates structured outputs (JSON/CSV), captures full command output to an evidence directory, and defines pass criteria for automated verification and human review.

Quick Start

Run the project build, locate or install the binary, then execute the primary command while saving stdout, stderr, and exit codes into the e2e-evidence directory.

Frequently Asked Questions about cli-validation

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

FAQPage Schema
How do I validate CLI binaries and capture stdout, stderr, and exit codes?▼

To validate CLI binaries and capture output, execute the command-line tool while directing stdout, stderr, and exit codes into a designated evidence directory for automated verification and human review.

What is the best way to verify command-line tool builds across different languages?▼

Verifying command-line tool builds across languages requires building or installing the executable for Rust, Go, Node.js, or Python projects, then running behavioral checks to confirm the produced binary operates correctly.

How do I test CLI error cases like invalid flags and missing arguments?▼

Testing CLI error cases involves executing the binary with invalid flags, missing arguments, file-not-found, and permission scenarios, capturing the resulting stderr and exit codes to confirm conventional error behavior.

Can I validate JSON and CSV output formats from command-line tools?▼

Yes, you can validate JSON and CSV structured outputs from command-line tools by checking parseability during execution and saving the full command output as evidence for downstream automated verification.

Does CLI testing work with stdin and pipe behavior validation?▼

CLI testing works with stdin and pipe behavior by exercising the command-line tool's input handling during execution, capturing the resulting stdout and stderr to verify correct data processing.

Related Skills

Explore More Software Engineering Skills→
iiammaeiiammae

devcontainer-setup

Generate Dockerfiles, devcontainer.json configurations, and post-install scripts for Python, Node, Rust, and Go projects.

Community
Advanced
matt-rileymatt-riley
1

verification-before-completion

Run exact verification commands and quote fresh output as evidence.

Community
Advanced
psdjungpulzzepsdjungpulzze

test-generator

Generate unit and integration test scaffolds with coverage gap analysis.

Community
Intermediate
modiqomodiqo
820

rote-shell

Execute commands, capture output, follow logs, and crystallize CLI work into TypeScript flows.

Official
Advanced