qa-sweep

Review git diff code changes and run tests for quality issues.

437|45|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill qa-sweep-zaxbyhub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-sweep
Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/qa-sweep
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill qa-sweep-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of shipping code with undetected bugs, regressions, or quality gaps by performing a focused, independent QA review of all code changes before they are published or merged.

Core Features & Use Cases

  • Focused Diff Review: Inspects all changed files directly (not just summaries) to identify code quality issues, bugs, and residual risks, with findings ranked by severity and linked to specific file/line references.
  • Targeted Validation: Runs focused test, lint, and validation commands matched to the modified code surface to catch regressions and enforce project engineering conventions.
  • Use Case: After completing a new feature implementation or bug fix, use this skill to run a pre-publish quality gate to confirm no existing functionality is broken and all required tests pass.

Quick Start

Use the qa-sweep skill to run a quality review of your recent code changes and identify any remaining risks before publishing.

Frequently Asked Questions about qa-sweep

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

FAQPage Schema
How do I run a pre-merge code review to catch regressions?

A pre-merge code review catches regressions by inspecting changed files directly and running targeted validation commands. This process identifies bugs and quality gaps, ranking findings by severity with specific file and line references before publication.

What is a QA sweep in software engineering?

A QA sweep is an independent quality assurance review of code changes performed post-implementation. It inspects code diffs directly to identify bugs, regressions, and quality gaps, applying severity rankings to findings before code is published or merged.

How do I check code diff quality before publishing changes?

To check code diff quality before publishing, perform a focused diff review that inspects changed files directly rather than summaries. This approach identifies residual risks and enforces engineering conventions through targeted test and lint commands.

Does a pre-merge quality gate require git diff outputs?

Yes, a pre-merge quality gate requires access to git diff outputs, project test runners, and engineering convention guidelines. These inputs allow the review process to deliver severity-ranked findings with accurate file and line references.

What is the best way to identify residual risks in modified code?

The best way to identify residual risks in modified code is running a focused QA review post-implementation. This method inspects all changed files directly and runs matched validation commands to catch bugs and enforce project conventions.

When do I need a focused regression check after bug fixing?

You need a focused regression check after bug fixing or completing feature implementation to ensure no existing functionality is broken. This pre-publish quality gate validates modified code surfaces and confirms all required tests pass.