skills.rest
WHITS-ISLAND
WHITS-ISLANDOFFICIAL
Explore all skills by this author →
GitHub

qa-check

Verify code changes against a QA checklist and output a Markdown status report.

1|Updated Jan 20, 2026
Search Tags:#automation#grep#code-review#bug-tracking#report-generation#qa-check
One-click install
npx skills add https://github.com/WHITS-ISLAND/inspirehub-mobile --skill qa-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-check
Source: https://github.com/WHITS-ISLAND/inspirehub-mobile/tree/main/.claude/skills/qa-check
Command: npx skills add https://github.com/WHITS-ISLAND/inspirehub-mobile --skill qa-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically verifies whether code changes satisfy the QA checklist and generates a structured report to guide releases and bug tracking.

Core Features & Use Cases

  • Automated verification: Scans the repository against docs/qa_checklist.md to determine which bugs are addressed.
  • Status reporting: Produces a Markdown table summarizing fixed, unresolved, and partially addressed issues.
  • Targeted checks: Allows focusing on a specific BUG-ID or applying the full checklist with "all".

Quick Start

Run the QA-check skill with a BUG-ID or "all" to generate a QA verification report against the current codebase.

Frequently Asked Questions about qa-check

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

FAQPage Schema
How do I automate code review against a QA checklist?▼

To automate code review against a QA checklist, use a tool that reads docs/qa_checklist.md, inspects relevant source files using grep, and generates a Markdown report summarizing fixed, unresolved, and partially addressed issues.

How do I generate a bug tracking report for specific code changes?▼

Generate a bug tracking report by running an automated verification check with a specific BUG-ID or applying it to all issues. The system inspects your codebase changes and produces a structured Markdown table summarizing the verification status.

What is automated QA verification for source files?▼

Automated QA verification for source files is the process of scanning code changes against a predefined checklist to determine which bugs are addressed, producing a structured status report to guide software releases.

Do I need a specific file format to run automated QA checks?▼

Yes, you need a docs/qa_checklist.md file in your repository to run automated QA checks. The verification process reads this Markdown file to understand the requirements before inspecting your source files.

Can I check a single bug ID instead of scanning the whole codebase?▼

Yes, you can check a single bug ID by providing the specific BUG-ID to the verification process. This allows targeted checks instead of applying the full checklist with the all command.

What format does an automated QA report generate?▼

An automated QA report generates a Markdown file format. This structured Markdown output summarizes verification statuses, detailing fixed, unresolved, and partially addressed issues in a clear table.

Related Skills

Explore More Software Engineering Skills→
AEtherlight-aiAEtherlight-ai

protect

Annotate passing code with protection levels and update policy documents.

Official
Intermediate
rafaelcostaf4-afkrafaelcostaf4-afk

pdf

Extract text and tables from PDFs into Markdown-ready chunks.

Community
Advanced
testomatiotestomatio
63

prompt-audit

Audit AI prompts and rules for contradictions, ambiguity, and incomplete guidance.

Official
Basic
cdubiel08cdubiel08
2

report

Generate markdown project status reports and post them to GitHub Projects V2.

Community
Advanced