qa

Automates git-diff-driven QA by scoping unit tests and regression checks to modified files and outputs a test_report with atomic fixes and a WTF gate.

36|4|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/xg-gh-25/SwarmAI --skill qa-xg-gh-25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/xg-gh-25/SwarmAI/tree/main/backend/skills/s_qa
Command: npx skills add https://github.com/xg-gh-25/SwarmAI --skill qa-xg-gh-25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-aware structured QA helps teams validate changes by running targeted tests on modified code, ensuring regressions are caught early and changes are well-regulated.

Core Features & Use Cases

  • Scope tests to changed files using git diff and artifact context.
  • Run unit tests and regression checks guided by design-docs and review artifacts.
  • Produce a test_report artifact and enforce atomic fixes with a WTF gate.

Quick Start

Run QA on your current branch to validate changes, execute unit tests, and produce a test report.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run regression tests only on modified files using git diff?

Diff-aware QA scopes regression checks to modified files identified via git diff. It consumes changeset artifacts to target only changed code, catching regressions early without requiring a full test suite run across the entire codebase.

What is diff-based quality assurance and when do I need it?

Diff-based quality assurance validates software changes by running targeted unit tests on modified code. Teams need it when using artifact workflows to catch regressions early without executing redundant tests on unchanged files.

How do I generate a test report from a git changeset and design doc?

You generate a test report by feeding the changeset and design_doc into the QA workflow. The process runs unit tests and regression checks on modified files, outputting a structured test_report artifact with atomic fixes.

Can I halt risky code changes automatically during unit testing?

Yes, the QA process enforces a WTF gate to halt risky changes automatically. After running diff-scoped unit tests, it evaluates the results and stops the workflow if the changes pose significant regression risks.

Does diff-aware testing work without external dependencies?

Yes, diff-aware testing operates with zero external dependencies. It functions by consuming internal artifact context like changesets and design docs to guide unit testing and regression checks within your existing workflow.

What is the best way to verify code changes using artifact workflows?

The best way is using diff-aware QA to apply artifact-guided verification across changes. It consumes changeset and review artifacts to execute targeted unit tests, producing a test report and enforcing atomic fixes for safe releases.