skills.rest
edercnj
edercnjCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

x-review-qa

Evaluate code changes for QA compliance across tests, coverage, and TDD practices.

Updated Aug 27, 2026
Search Tags:#automation#tdd#code-review#test-coverage#qa-review#pr-quality
One-click install
npx skills add https://github.com/edercnj/ia-dev-environment --skill x-review-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: x-review-qa
Source: https://github.com/edercnj/ia-dev-environment/tree/main/src/main/resources/claude/skills/x-review-qa
Command: npx skills add https://github.com/edercnj/ia-dev-environment --skill x-review-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review code changes for QA compliance, ensuring test coverage, proper TDD flow, naming consistency, fixture usage, and acceptance-criteria coverage during PR reviews.

Core Features & Use Cases

  • Validate test coverage thresholds and naming conventions across changed files
  • Enforce TDD progression and fixture centralization in PRs
  • Provide actionable QA feedback and a final score to guide reviewers

Quick Start

Provide the PR diff or file paths to initiate a QA compliance review.

Frequently Asked Questions about x-review-qa

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

FAQPage Schema
How do I validate test coverage thresholds in a pull request?▼

Validate test coverage thresholds in a pull request by providing the PR diff or file paths to evaluate changed files against configured coverage limits, ensuring new code meets minimum test requirements before merging.

What is TDD progression and how is it enforced during code review?▼

TDD progression during code review is the validation of test-driven development flow, ensuring tests are written and updated alongside code changes. It enforces proper TDD practices by analyzing changed test files and source code within the PR workflow.

How do I check if my test naming conventions and fixture usage meet QA compliance?▼

Check test naming conventions and fixture usage by running a QA compliance review on your code changes. This analyzes changed files to enforce consistent naming patterns and verifies proper fixture centralization across the test suite.

Can I map acceptance criteria to tests for pre-merge quality gates?▼

Yes, you can map acceptance criteria to tests for pre-merge quality gates. The review process analyzes code changes to verify that acceptance criteria are properly covered within a generated QA checklist, guiding reviewers before merging.

Does the QA review process provide an actionable score for PR reviewers?▼

Yes, the QA review process provides an actionable final score for PR reviewers. It evaluates code changes for test coverage, TDD practices, and naming consistency, delivering targeted feedback to guide pre-merge quality decisions.

Related Skills

Explore More Software Engineering Skills→
MODAC-AgentMODAC-Agent

gosu-review-v1

Generate Korean Markdown code-review reports from changed Go files.

Official
Advanced
jovermierjovermier
1

data-integrity-guardian

Analyze database migrations for referential integrity and transaction boundary issues.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

quality-run-linters

Run Mojo format, markdownlint, and pre-commit hooks for code quality checks.

Official
Intermediate
zapabobzapabob
2

test-gen

Generate unit, integration, and e2e test suites with 80% code coverage.

Community
Intermediate