generate-qa-checklist

Generates a QA test checklist from the three-dot git diff against develop.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/lucaszhh/agents --skill generate-qa-checklist-lucaszhh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-qa-checklist
Source: https://github.com/lucaszhh/agents/tree/main/skills/generales/generate-qa-checklist
Command: npx skills add https://github.com/lucaszhh/agents --skill generate-qa-checklist-lucaszhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? QA teams often receive vague handoffs after a feature branch is finished, forcing testers to read code or PRs to figure out what to verify. This Skill analyzes the branch's own changes and produces a self-contained qa_checklist.md with concrete, screen-verifiable test cases. ## Core Features & Use Cases - Three-dot diff analysis: Compares the branch against the merge-base with develop so only the branch's own changes are considered, avoiding flows from unrelated merged work. - Structured test matrices: Maps direct flows into tables covering happy path, edge cases, and negative cases, plus a regression section for components sharing modified types or utilities. - Environment preconditions: Detects new environment variables and feature flags so QA can configure the test environment before starting. - Use Case: After finishing a feature branch that modifies a selection component and adds a validation guard, run this Skill to produce qa_checklist.md with per-flow test tables and regression smoketest suggestions ready to hand to the QA team. ## Quick Start Ask the agent to generate the QA checklist for the current branch against develop and write it to qa_checklist.md.

Frequently Asked Questions about generate-qa-checklist

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

FAQPage Schema
How do I generate a QA test checklist from a git branch?▼

Run the Skill on your feature branch and it computes the three-dot diff against develop, identifies affected user flows, and writes a qa_checklist.md file with test case tables covering happy paths, edge cases, and negative scenarios.

What is the difference between two-dot and three-dot git diff for QA?▼

A three-dot diff compares your branch against the merge-base with develop, showing only your branch's own changes. A two-dot diff includes changes merged into develop by others, which would add unrelated flows to the checklist.

Does the checklist include regression test suggestions?▼

Yes. The Skill inspects imports in the diff to find unmodified components that share changed types, utilities, or services, and lists them in a regression smoketest section with a one-line justification for each.

Can the checklist capture environment variables and feature flags?▼

Yes. When the diff introduces environment variables, .env.example entries, or boolean feature flags, they are declared as infrastructure preconditions so QA configures the environment before testing.

When should I not use this QA checklist generator?▼

Do not use it to write PR descriptions or technical reports, to update CHANGELOG release notes, or to run automated unit tests. It only produces a manual verification checklist document from branch changes.