qa-cli

Run phase-driven checks to verify CLI tool behavior and outputs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CLI tools often suffer from unclear behavior, inconsistent outputs, and brittle workflows. QA-cli orchestrates phase-driven checks that reveal gaps in help, flags, output formats, and error handling.

Core Features & Use Cases

  • Phase-driven survey of structure, function, data, interfaces, and operations to map risk.
  • Sub-agent checks that execute deterministic command sequences and report pass/fail with transcripts.
  • Oracle-style evaluation (familiarity, explainability, history, claims, product, purpose, standards) to ensure documentation alignment.
  • Fresh-eyes review to surface usability and UX ambiguities.

Quick Start

Run qa-cli on a target CLI tool to begin Phase 1 survey.

Frequently Asked Questions about qa-cli

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

FAQPage Schema
How do I automate CLI testing for error paths and happy paths?

Automated CLI testing for error and happy paths runs through phase-driven checks, executing deterministic command sequences via sub-agents to report pass/fail results with full transcripts and actionable remediation guidance.

What is oracle evaluation in CLI quality assurance?

Oracle evaluation in CLI quality assurance verifies documentation alignment by checking familiarity, explainability, history, claims, product, purpose, and standards to ensure predictable outputs and enforce standard CLI conventions.

How do I run systematic QA checks to find inconsistent outputs in my CLI tool?

Systematic QA checks map risk through a Phase 1 survey of structure, function, data, interfaces, and operations, followed by sub-agent checks, oracle evaluation, fresh-eyes review, and regression reporting to reveal gaps in flags and output formats.

Can I use this phase-driven workflow for testing CLI tools with no external dependencies?

Yes, this phase-driven workflow for testing CLI tools operates with no external dependencies, surveying behavior and verifying it through automated checks that cover happy paths, error paths, and edge cases without requiring additional setup.

What's the best way to surface usability ambiguities in command line tools?

The best way to surface usability ambiguities in command line tools is a fresh-eyes review phase, which identifies UX gaps and unclear behavior alongside deterministic command sequence checks and regression reporting.

Why does my CLI tool have brittle workflows and unclear behavior during testing?

Brittle workflows and unclear behavior during CLI testing stem from gaps in help, flags, output formats, and error handling, which phase-driven QA checks reveal through structured survey, sub-agent execution, and oracle evaluation.