qa

Automate QA validation, reporting, and stage-flow governance for development cycles.

5|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/GrinRus/ai_driven_dev --skill qa-grinrus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/GrinRus/ai_driven_dev/tree/main/skills/qa
Command: npx skills add https://github.com/GrinRus/ai_driven_dev --skill qa-grinrus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA stage validation and reporting for software development pipelines, automating the verification of changes and generating structured QA results.

Core Features & Use Cases

  • Automated QA orchestration across stage chains (idea → research → plan → QA) with canonical runtime.
  • Generates and validates QA reports, applies actions, and updates stage results within aidd reports.
  • Use case: before shipping a feature, run QA to verify tests, logs, and stage-status, then generate qa.actions.json for orchestration.

Quick Start

Trigger the QA stage for the current ticket to execute tests and generate the QA report.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate QA validation and reporting across software development stages?

Automated QA validation runs across stage-chains like idea, research, plan, and QA to verify changes. It generates structured QA reports, applies actions, and updates stage results within development pipelines.

What is stage-flow governance and how does it work for CI pipelines?

Stage-flow governance enforces action-contracts via qa.actions.json to control CI progression. It uses canonical stage runtime to validate test discovery and enforce loop mode before advancing software development cycles.

Can I use loop mode for test discovery and continuous QA orchestration?

Yes, loop mode supports continuous test discovery and QA orchestration. It applies canonical runtimes to validate tests, process logs, and generate canonical stage results for each ticket in the pipeline.

Does this QA orchestration tool work without external dependencies?

Yes, the QA orchestration runtime operates without external dependencies. It handles automated test execution, report generation, and action-contract enforcement internally to validate software changes.

What's the best way to generate qa.actions.json for automated testing workflows?

Trigger the QA stage for the current ticket to execute tests and generate the QA report. The runtime validates tests, logs, and stage-status, then outputs qa.actions.json to orchestrate downstream actions.

Why does my QA stage validation fail to update stage results in the pipeline?

QA stage validation requires canonical runtime execution and action-contract enforcement to update stage results. Ensure loop mode and test discovery are properly configured to generate valid qa.actions.json outputs.