Verified:GitHub

qa-analyze

Translate project requirements and code behavior into discrete, verifiable assertions and generate a Markdown QA analysis report in _qa/.

Updated Apr 6, 2026

Search Tags:#code-quality #risk-assessment #assertions #test-coverage #requirements-traceability #qa-report #qa-analyze

Ready to run

npx skills add https://github.com/mgeer/qa-skills --skill qa-analyze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-analyze
Source: https://github.com/mgeer/qa-skills/tree/main/qa-analyze
Command: npx skills add https://github.com/mgeer/qa-skills --skill qa-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The QA Analyze skill translates project requirements and code behavior into clear, testable assertions, exposing gaps between what is required and what is tested.

Core Features & Use Cases

Translate requirements, specs, and code into discrete assertions that humans can review.
Produce a single, human-readable QA analysis report that documents coverage gaps, ambiguities, and risks.
Operate in scoped or full-project mode and assemble artifacts for downstream skills (qa-cover, qa-review, qa-mutate).

Quick Start

Analyze the target module or the entire project and generate the _qa/qa-analysis.md report.

Frequently Asked Questions about qa-analyze

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

FAQPage Schema

How do I translate project requirements into testable assertions to find coverage gaps?▼

To translate project requirements into testable assertions, you analyze requirements and code behavior to identify discrete, verifiable statements. This process exposes coverage gaps, ambiguities, and risks by comparing required behavior against actual test execution.

What is requirements traceability and how does it help with risk assessment?▼

Requirements traceability maps project specifications to discrete assertions to evaluate test coverage. It supports risk assessment by prioritizing modules with significant change history, ensuring critical behavior is verified and coverage gaps are explicitly documented.

Can I analyze test coverage for a scoped module instead of a full project?▼

Yes, you can analyze test coverage for a scoped module instead of a full project. The analysis operates in either scoped or full-project mode, prioritizing areas with the most significant risk or change history to target specific coverage gaps.

How do I generate a QA report that documents requirements coverage gaps?▼

To generate a QA report documenting requirements coverage gaps, you analyze the target code and produce a single Markdown file in the _qa/ directory. This report includes a structured assertion table, frontmatter, and a human-friendly narrative for review.

What is the best way to prepare code behavior analysis for downstream QA skills?▼

The best way to prepare code behavior analysis for downstream QA skills is to generate a structured Markdown report containing verifiable assertions and coverage gap artifacts. This output supports downstream processes like qa-cover, qa-review, and qa-mutate.