skills.rest
mkrlabs
mkrlabsOFFICIAL
Explore all skills by this author →
Website𝕏@MakerLabsDevGitHub

qa-report-contract

Generate structured QA verdicts and metrics for validation workflows.

Updated Apr 22, 2026
Search Tags:#workflow#validation#qa#verification#report#contract
One-click install
npx skills add https://github.com/mkrlabs/specflow --skill qa-report-contract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-report-contract
Source: https://github.com/mkrlabs/specflow/tree/main/examples/.claude/skills/qa-report-contract
Command: npx skills add https://github.com/mkrlabs/specflow --skill qa-report-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This structured QA report contract is preloaded into QA agents so workflow audits can read verdicts, test counts, and bug totals directly from the ledger.

Core Features & Use Cases

  • QA SUMMARY block must be appended exactly once before the workflow status block.
  • Rules define QA_VERDICT as pass | fail | blocked and require explicit numeric fields.
  • Alignment With Workflow Status ensures QA outputs drive handoffs between QA and development teams.
  • Use Case: QA validation, test coverage reporting, and post-fix verification.

Quick Start

Preload the QA contract into your QA harness and run a validation workflow to generate and attach the QA summary.

Frequently Asked Questions about qa-report-contract

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

FAQPage Schema
How do I generate structured QA verdicts for automated validation workflows?▼

A QA SUMMARY block provides structured test counts, bug totals, and QA verdicts directly within your workflow ledger. It must be appended exactly once before the workflow status block to ensure outputs drive team handoffs.

How do I automate post-fix verification reporting in CI pipelines?▼

Automate post-fix verification reporting in CI pipelines by applying the QA contract to your validation runs. This generates an auditable report with clear verdict criteria and explicit numeric fields satisfying workflow state requirements.

Does this QA reporting contract require specific dependencies to work with test coverage reports?▼

This structured QA report contract distinguishes itself by defining strict QA_VERDICT rules as pass, fail, or blocked, and requiring explicit numeric fields. This ensures outputs drive handoffs between QA and development teams better than standard reporting.

When should I not use a structured QA report contract for workflow validation?▼

You should not use a structured QA report contract when your workflow does not require auditable ledger entries or strict pass|fail|blocked verdict criteria. It is specifically designed for QA validation, test coverage reporting, and post-fix verification runs.

Related Skills

Explore More Data & Analytics Skills→
kevintsengtwkevintsengtw
28

dotnet-testing-code-coverage-analysis

Measure and interpret .NET code coverage with Coverlet and ReportGenerator.

Community
Intermediate
fatihfatih
884

pr-comments

Fetch GitHub PR comments, review comments, and reviews for the current branch.

Community
Advanced
PantaniPantani
30

tdmcp-test-coverage

Run coverage harnesses, parse results, and spawn targeted test writers.

Community
Advanced
CaptainCrouton89CaptainCrouton89
497

Testing Code

Automate software tests to verify functionality against acceptance criteria.

Community
Basic