skills.rest
sahajamoth
sahajamothCOMMUNITY
Explore all skills by this author →
GitHub

qa-officer

Reviews code changes for adequate test coverage and QA quality compliance.

Updated Aug 23, 2026
Search Tags:#testing#qa#best-practices#quality-assurance#code-review#software#test-coverage
One-click install
npx skills add https://github.com/sahajamoth/apex --skill qa-officer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-officer
Source: https://github.com/sahajamoth/apex/tree/main/.agents/skills/qa-officer
Command: npx skills add https://github.com/sahajamoth/apex --skill qa-officer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA Officer helps ensure code changes come with adequate tests and meet QA standards, reducing release risk.

Core Features & Use Cases

  • Review new code for test coverage, quality, and adherence to project QA guidelines.
  • Identify gaps in tests, flaky tests, or missing edge-case scenarios, and reference specific files.
  • Provide concrete recommendations and file-and-line references to bring parity with the checklist.

Quick Start

Review a recent PR by running a QA officer checklist against the repository and report gaps with file references.

Frequently Asked Questions about qa-officer

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

FAQPage Schema
How do I ensure new code changes have adequate test coverage before release?▼

To ensure adequate test coverage, you can review code changes against a QA checklist to verify tests exist, pass, and align with project standards. This process identifies gaps, flaky tests, and missing edge-case scenarios with specific file references.

What is the best way to enforce test quality during a pull request review?▼

The best way to enforce test quality during a pull request review is to run a QA checklist against the repository. This evaluates new features, bug fixes, and migrations, reporting coverage gaps and providing concrete recommendations with file-and-line references.

How do I check if #[cfg(test)] mod tests are present inside each file?▼

To check if #[cfg(test)] mod tests are present inside each file, apply a QA review checklist to the code changes. This enforces the requirement that tests exist within each file and prohibits modifications to production code during the review.

Can I review bug fixes and migrations for missing edge-case scenarios?▼

Yes, you can review bug fixes and migrations for missing edge-case scenarios by applying a QA officer checklist. It identifies gaps in tests, flaky tests, or missing edge cases, and references specific files to bring parity with the checklist.

Why should production code not be modified during a test coverage review?▼

Production code should not be modified during a test coverage review to strictly isolate quality assurance checks from implementation changes. This enforces project standards by ensuring the review process only evaluates existing code and test parity.

Related Skills

Explore More Software Engineering Skills→
lgzarturolgzarturo

cc-review

Collect Git diffs and evaluate changes against a structured review checklist.

Community
Advanced
ihj04982ihj04982

test-coverage

Analyzes JSON coverage reports and generates missing tests for files under 80% coverage.

Community
Advanced
FaisalAlqarniFaisalAlqarni
5

springboot-verification

Automate build, static analysis, testing, and security scanning for Spring Boot projects.

Community
Advanced
openharmonyinsightopenharmonyinsight
31

ai-generated-ut-code-review

Score AI-generated unit test code for coverage and robustness.

Official
Intermediate