qa-review

Reviews diffs, branches, and pull requests across correctness, security, performance, and style lanes.

Updated Feb 26, 2025
One-click install
npx skills add https://github.com/adschill/dev-config --skill qa-review-adschill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-review
Source: https://github.com/adschill/dev-config/tree/main/skills/qa-review
Command: npx skills add https://github.com/adschill/dev-config --skill qa-review-adschill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It catches actionable regressions, security flaws, performance issues, and maintainability problems in code changes before they are merged, replacing ad-hoc manual review with a structured multi-lane process. ## Core Features & Use Cases - Four-lane parallel review: Spawns read-only reviewer subagents covering correctness, security, performance/build/runtime, and style/maintainability, then validates every finding against the actual diff. - Scoped diff analysis: Reviews staged and unstaged changes, branches, tickets, pull requests, or commit ranges with automatic base-branch detection and ticket-key session naming. - Verification and severity triage: Discovers project checks from package.json, Makefile, pyproject.toml, and CI configs, runs matching checks, and reports findings with Blocker-to-Nit severity levels and evidence. - Use Case: Before merging a feature branch, invoke $qa-review to receive a validated report of only the issues caused by your change, with precise file-and-line evidence and suggested fixes. ## Quick Start Ask the assistant to run $qa-review on the current branch or pull request to get a validated pre-merge findings report.

Frequently Asked Questions about qa-review

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

FAQPage Schema
How do I review a pull request before merging?▼

Invoke $qa-review with the pull request as the target. It detects the PR base branch, gathers the full diff, runs four parallel review lanes, and returns a severity-ranked report of validated findings with file-and-line evidence.

How to QA staged and unstaged git changes?▼

Run $qa-review on the working tree; it starts with git status, git diff --stat, and git diff --cached --stat to cover both staged and unstaged changes. It records whether uncommitted changes are included and ignores unrelated pre-existing issues.

What does the qa-review skill check in a code change?▼

It covers four lanes: correctness (regressions, error handling, missing tests), security (auth, injection, secrets, trust boundaries), performance/build/runtime (hot paths, packaging, dependencies), and style/maintainability (conventions, superfluous helpers, test hygiene).

Does qa-review run tests and builds automatically?▼

Yes, it discovers standard project checks from files like package.json, Makefile, pyproject.toml, Cargo.toml, and CI configuration, then runs non-fixing checks matching the changed surface and risk, reporting exact pass/fail commands.

When should I not use qa-review?▼

Do not invoke it for ordinary coding tasks or change requests; it is designed only for explicit pre-merge review of diffs, branches, tickets, or pull requests. It activates only when the user directly asks for QA, validation, or merge-checking.