sumo-qa-finishing-qa-work

Capture fresh test evidence, coverage snapshots, and risk-to-test mappings into a markdown QA summary.

5|1|Updated May 12, 2026
One-click install
npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-finishing-qa-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sumo-qa-finishing-qa-work
Source: https://github.com/sumithr/sumo-qa/tree/main/skills/sumo-qa-finishing-qa-work
Command: npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-finishing-qa-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns the end of a QA rollout into a defensible, reviewer-ready evidence package by re-running the suite, mapping risks to tests, and writing a durable summary.

Core Features & Use Cases

  • Fresh evidence capture: Runs a full suite in the current turn and blocks finishing on failing tests to prevent stale “CI was green” claims.
  • Coverage and traceability: Produces a coverage snapshot (when available) and a risk-to-test map so reviewers can verify what was exercised.
  • Gap and follow-up honesty: Records known gaps, open follow-ups, and any relevant xfail state so the PR has a clear next-step list.

Quick Start

Use sumo-qa-finishing-qa-work at the end of your QA rollout to generate the run summary and propose a PR description from the captured evidence.

Frequently Asked Questions about sumo-qa-finishing-qa-work

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

FAQPage Schema
How do I generate reviewer-grade QA evidence for a pull request?

To generate reviewer-grade QA evidence, run a fresh full test suite, capture a coverage snapshot, and draft a markdown PR summary mapping risks to tests. This produces durable, defensible documentation of what was exercised before opening the pull request.

What is risk-to-test mapping in a QA rollout?

Risk-to-test mapping links specific code change risks to the exact tests that exercise them. It helps reviewers verify coverage and traceability by proving potential failure points are validated by the current test suite run.

Can I finish QA documentation if my test suite has failing tests?

You cannot finish QA documentation if your test suite has failing tests. The finishing process blocks on failing tests to prevent stale CI claims, requiring a fully green run before generating the PR summary.

How do I document known gaps and follow-ups for a PR summary?

Document known gaps and follow-ups by recording missing coverage, open items, and xfail states in a written markdown summary. This gives reviewers a clear next-step list and prevents hidden technical debt.

Does TDD gating require fresh evidence before drafting a PR summary?

TDD gating requires fresh evidence before drafting a PR summary by enforcing a full-suite run in the current turn. This ensures test-driven development claims are backed by current coverage snapshots rather than stale CI results.

What's the best way to store QA run summaries for future reference?

The best way to store QA run summaries is writing the markdown output to docs/qa/runs/<date>-<feature>.md. This creates a durable, reviewer-ready evidence package capturing fresh test results and risk-to-test traceability.