qa-cli

Audit CLI tools via black-box testing and generate evidence-backed QA reports.

1|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/laststance/skills --skill qa-cli-laststance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-cli
Source: https://github.com/laststance/skills/tree/main/skills/qa-cli
Command: npx skills add https://github.com/laststance/skills --skill qa-cli-laststance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits CLI tools without touching their source code and outputs a structured QA report with evidence for each finding.

Core Features & Use Cases

  • Black-box QA workflow for CLI tools including baseline instrumentation, surface mapping, golden-path validation, error surface inspection, I/O testing, and signal/cleanup checks, all compiled into a single report.
  • Use Case: A developer wants an automated, repeatable QA pass on a new CLI tool before release to catch help text inconsistencies, flag parsing issues, JSON output validity, and config precedence.

Quick Start

Run qa-cli against your CLI tool to generate a standardized QA report.

Frequently Asked Questions about qa-cli

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

FAQPage Schema
How do I run black-box QA testing on a CLI tool without touching its source code?

Black-box QA testing for a CLI tool audits subcommands, flags, output formats, and signal handling without touching source code, producing an evidence-backed report with a health score and top fixes.

What is the best way to automate CLI testing and validate JSON output formats?

Automated CLI testing validates JSON output formats by capturing stdout, stderr, and exit codes during a structured workflow, checking format validity and color/no-color behavior to compile evidence-backed findings.

How does a QA CLI audit handle environment and config precedence validation?

A QA CLI audit validates environment and config precedence by testing input handling and flag parsing across sessions, capturing artifacts as evidence to document issues in a structured report.

Can I generate a standardized QA report with a health score for my bash CLI tool?

You can generate a standardized QA report for a bash CLI tool that includes a health score, top 3 fixes, and a residue section by running a structured Phase 0-9 black-box testing workflow.

What signal handling and cleanup checks are included in a CLI black-box audit?

A CLI black-box audit inspects signal handling and cleanup checks by sending signals during execution, capturing the resulting session artifacts and exit codes as evidence for the final report.

Why does my CLI tool fail the help text and flag parsing consistency check?

Help text and flag parsing inconsistencies surface during the surface mapping and golden-path validation phases of a CLI audit, capturing exact stdout and stderr evidence to document the specific issues.