manual-qa

Automate end-to-end manual QA for CLI workflows using a release binary and temp project.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/JYC11/filament --skill manual-qa-jyc11
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manual-qa
Source: https://github.com/JYC11/filament/tree/main/.claude/skills/manual-qa
Command: npx skills add https://github.com/JYC11/filament --skill manual-qa-jyc11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual QA exercises the real CLI against a temporary project to surface output quality, error messaging, and workflow gaps.

Core Features & Use Cases

  • End-to-end QA across Init, CRUD, and error handling to validate usability and reliability.
  • Verifies JSON output mode, edge cases, and cross-command workflows.
  • Uses a test-plan and results workflow to guide testing and capture outcomes.

Quick Start

Build the release binary, initialize a temporary QA project, run the manual-qa workflow against the binary, and record results to .qa/manual-qa-results.md.

Frequently Asked Questions about manual-qa

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

FAQPage Schema
How do I perform manual QA testing for a CLI workflow?▼

Manual QA testing for a CLI workflow is performed by driving a release binary through a real, temporary project to validate usability and reliability across init, CRUD, and error handling scenarios. It requires a test plan template and a results recording workflow to capture outcomes.

What is a CLI test plan used for in end-to-end manual QA?▼

A CLI test plan in end-to-end manual QA is used to guide testing across cross-command workflows, edge cases, and JSON output mode, ensuring that output quality and workflow gaps are systematically surfaced and recorded.

How do I record manual QA results for command-line interface testing?▼

You record manual QA results for command-line interface testing by running the QA workflow against the binary and writing the outcomes to a results file at .qa/manual-qa-results.md, capturing both strict JSON and human-readable outputs.

Does manual QA testing work with JSON output mode and cross-command workflows?▼

Yes, manual QA testing works with JSON output mode and cross-command workflows by verifying edge cases and validating the reliability of sequential command execution within a temporary project environment.

What do I need to set up before testing CLI workflows with a manual QA process?▼

Before testing CLI workflows with a manual QA process, you need to build the release binary, initialize a temporary QA project, and prepare a test plan template to guide the execution and recording workflow.

When should I use manual QA instead of automated tests for CLI tools?▼

You should use manual QA instead of automated tests for CLI tools when you need to exercise the real binary against a temporary project to specifically surface output quality, error messaging clarity, and workflow usability gaps.