qa-aqa

Define static analysis, automated test, and manual verification gates for QA workflows.

1|Updated Mar 26, 2026

Search Tags:#automation #testing #qa #test-generation #quality-assurance #acceptance-criteria #manual-verification

Ready to run

npx skills add https://github.com/euroconic/noter --skill qa-aqa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-aqa
Source: https://github.com/euroconic/noter/tree/main/skills/qa-aqa
Command: npx skills add https://github.com/euroconic/noter --skill qa-aqa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA is often an afterthought, causing regressions and unstable releases. This skill defines a scalable QA framework with automated gates, checklists, and guidance to enforce quality at every commit and feature change.

Core Features & Use Cases

Defines a three-level QA gate: static analysis, automated tests, and manual verification to ensure code quality end-to-end.
Provides a reusable template for acceptance criteria, checklists, and sign-offs that guide engineers and QA across features, bug fixes, and security changes.
Enables automated test generation from acceptance criteria to improve coverage and consistency across releases.

Quick Start

Start the QA workflow at the beginning of a feature, setting up gates and checklists for the upcoming change.

Frequently Asked Questions about qa-aqa

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

FAQPage Schema

How do I set up quality gates for automated testing and manual verification?▼

Acceptance criteria are codified using a reusable template that guides engineers and QA through checklists and sign-offs. This structured format applies across features, bug fixes, and security changes to ensure consistent automated and manual checks.

Can I generate automated tests from acceptance criteria?▼

This QA framework is applicable to every feature, bug fix, and security change. It scales by providing reusable templates for acceptance criteria, checklists, and sign-offs that guide both engineers and QA across the development lifecycle.

What is the best way to enforce minimum test coverage across releases?▼

The best way to enforce minimum test coverage is by codifying blocking conditions within a three-level QA gate. This framework ensures every feature passes static analysis, automated tests, and manual verification before release.

When should I apply manual verification gates instead of automated tests?▼

Manual verification gates should be applied alongside automated tests for every feature, bug fix, and security change. The framework defines blocking conditions for both automated and manual checks to ensure end-to-end quality assurance.