skills.rest
assertchris
assertchrisCOMMUNITY
Explore all skills by this author →
𝕏@assertchrisGitHub

custom-qa-checklist

Generate a manual QA test checklist from feature documentation for the current branch.

2|1|Updated Feb 19, 2026
Search Tags:#automation#testing#documentation#checklist#qa#feature
One-click install
npx skills add https://github.com/assertchris/claude-skills --skill custom-qa-checklist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: custom-qa-checklist
Source: https://github.com/assertchris/claude-skills/tree/main/custom-qa-checklist
Command: npx skills add https://github.com/assertchris/claude-skills --skill custom-qa-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of manual QA test checklists by extracting user-facing functionality from feature documentation, saving QA engineers time and ensuring comprehensive test coverage.

Core Features & Use Cases

  • Automated Checklist Generation: Creates focused QA checklists from feature documentation.
  • User-Facing Focus: Extracts only testable items visible in a browser, ignoring backend details.
  • Use Case: When a new feature is ready for testing, use this Skill to quickly generate a checklist of all the user-facing aspects that need to be manually verified in the application.

Quick Start

Generate a QA checklist for the current feature branch.

Frequently Asked Questions about custom-qa-checklist

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

FAQPage Schema
How do I generate a manual QA checklist from feature documentation?▼

A QA checklist from feature documentation extracts user-facing functionality, UI elements, user flows, edge cases, and error states for browser testing. It ignores automated test instructions and backend details to focus purely on manual verification steps.

What is included in a QA test checklist generated from feature docs?▼

A generated QA checklist includes user-facing functionality, UI elements, user flows, edge cases, and error states visible in a browser. It specifically excludes backend implementation details and automated test instructions to focus only on manual verification.

How do I extract user-facing functionality from documentation for testing?▼

You extract user-facing functionality for testing by parsing feature documentation to identify UI elements and user flows. This process isolates browser-testable items and filters out backend implementation details and automated test instructions.

Does this QA checklist generation approach work for automated test instructions?▼

No, this approach does not work for automated test instructions. It is designed specifically to extract manual browser testing items and actively excludes automated test instructions and backend implementation details from the generated checklist.

Can I use feature documentation to create browser testing checklists for a specific branch?▼

Yes, you can use feature documentation to create browser testing checklists for a specific branch. The process reads docs for the current branch and extracts relevant UI elements, user flows, and error states for manual QA verification.

Related Skills

Explore More Software Engineering Skills→
ybbms777ybbms777
1

test-browser

Automate end-to-end browser tests for pages affected by Git branch changes.

Community
Advanced
Michal-J-KolodziejMichal-J-Kolodziej

functional-test

Automate browser-based functional testing of dashboard routes and log defects to DASHBOARD_BUGS.md.

Community
Advanced
pur3v4d3rpur3v4d3r
6

senior-qa

Generate test suites, analyze coverage, and scaffold E2E tests for React, Next.js, and Node.js projects.

Community
Advanced
figuedmundofiguedmundo

senior-qa

Generates test suites, analyzes coverage, and scaffolds E2E tests for ReactJS, NextJS, and NodeJS.

Community
Advanced