qa

Define test strategies, coverage targets, and pre-merge gates for CI pipelines.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/ResearchMonkey/Foundation_template --skill qa-researchmonkey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/ResearchMonkey/Foundation_template/tree/main/.agent/skills/qa
Command: npx skills add https://github.com/ResearchMonkey/Foundation_template --skill qa-researchmonkey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quality assurance guidance to improve test strategy, coverage visibility, and gate enforcement, so teams ship reliable software.

Core Features & Use Cases

  • Define and enforce test strategies (unit, integration, E2E) and associated coverage targets.
  • Conduct proactive test quality audits to catch missing edge cases, flaky tests, and misaligned requirements.
  • Monitor and govern pre-merge gates to prevent regressions and ensure test health across the CI pipeline.

Quick Start

Ask the QA agent to review the current tests for a feature and propose actionable improvements to coverage and quality gates.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I establish a test strategy across unit, integration, and E2E workflows?▼

To establish a test strategy, define specific test types and coverage targets for unit, integration, and E2E workflows, ensuring robust health monitoring and pre-merge gate enforcement across CI pipelines to prevent regressions.

What is the best way to enforce pre-merge gates and prevent flaky tests in CI pipelines?▼

Enforce pre-merge gates by monitoring CI pipeline test health, implementing audit routines to catch flaky tests, and applying guardrails that block regressions before merging software changes.

Can I use this to conduct test quality audits for missing edge cases?▼

Yes, you can conduct proactive test quality audits to identify missing edge cases, detect flaky tests, and correct misaligned requirements within your existing software project workflows.

How do I define coverage targets and monitor test health for regressions?▼

Define coverage targets by specifying requirements for unit, integration, and E2E tests, then monitor ongoing test health through routine audits and pre-merge gates to prevent regressions.

Does this approach work for guiding test strategy development in existing CI pipelines?▼

Yes, it applies to unit, integration, and end-to-end testing workflows across existing CI pipelines, guiding strategy development and specifying requirements for audit routines and coverage targets.