qa-verification

Name: qa-verification
Availability: InStock
Author: klabo

Record QA evidence and verification checklists for web UI and CLI tasks.

Updated Dec 31, 2025

Search Tags:#ui #qa #cli #verification #evidence #ci #tests

Ready to run

npx skills add https://github.com/joelklabo/markdowntown-cli --skill qa-verification-joelklabo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-verification
Source: https://github.com/joelklabo/markdowntown-cli/tree/main/codex/skills/qa-verification
Command: npx skills add https://github.com/joelklabo/markdowntown-cli --skill qa-verification-joelklabo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified QA verification for both web UI and CLI tasks, ensuring consistent evidence collection and faster validation.

Core Features & Use Cases

Collects QA evidence for UI and CLI changes (tests, logs, screenshots, CI status).
Provides a structured checklist for web UI verification and CLI verification.
Produces audit-ready documentation for releases and stakeholder reviews.

Quick Start

Run the QA verification workflow against the target change and record the required evidence in the task.

Frequently Asked Questions about qa-verification

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

FAQPage Schema

How do I collect QA evidence for both web UI and CLI tasks?▼

To collect QA evidence for web UI and CLI tasks, apply a unified verification checklist that captures required artifacts, logs, and CI status. This ensures consistent validation and audit-ready documentation before task closure.

What is unified QA verification for UI and CLI workflows?▼

Unified QA verification is a structured process that applies a standardized checklist to both web UI flows and CLI commands. It records tests, screenshots, and CI status to produce audit-ready documentation for releases.

How do I document QA evidence in tasks before closure?▼

Document QA evidence in tasks by capturing required artifacts, logs, and CI status using standardized formats and references. The verification checklist ensures all UI and CLI evidence is recorded before task closure.

Does this QA verification workflow support CI status checks?▼

Yes, this QA verification workflow captures CI status as part of its evidence collection process. It records CI status alongside UI and CLI test artifacts to ensure comprehensive validation before closure.

Can I use a single checklist for web UI verification and CLI verification?▼

Yes, you can use a single structured checklist for both web UI and CLI verification. It standardizes evidence collection across both interfaces, capturing required artifacts, logs, and CI status for consistent validation.

Why does my task need standardized formats for QA evidence?▼

Tasks need standardized formats for QA evidence to ensure consistent documentation and audit-ready references for stakeholder reviews. Standardized formats guarantee that UI and CLI verification artifacts are uniformly recorded before closure.