qa

Automate QA test decisions, regression contracts, and feature classification across repositories.

Updated Feb 25, 2026

Search Tags:#automation #testing #quality assurance #ci/cd #qa #regression

Ready to run

npx skills add https://github.com/perfectuser21/cecelia --skill qa-perfectuser21

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/perfectuser21/cecelia/tree/main/packages/quality/skills/qa
Command: npx skills add https://github.com/perfectuser21/cecelia --skill qa-perfectuser21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill acts as a central Quality Assurance controller, standardizing test decisions, regression contracts, and feature classification across multiple code repositories.

Core Features & Use Cases

Cross-repo QA Management: Unifies test strategy, regression contracts, Golden Paths, and feature categorization.
Automated Decision Making: Intelligently determines testing plans, RCI inclusion, and Golden Path suitability based on repository type and stage.
Use Case: When a new feature is developed, this Skill can determine if it needs to be added to the regression contract, classified as a new feature, and what tests should be run for the associated Pull Request.

Quick Start

Use the qa skill to determine what tests should be run for the current PR.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automate cross-repository QA decisions for a new pull request?▼

Automated cross-repository QA decisions are unified by evaluating repository type and development stage to intelligently determine necessary tests, RCI inclusion, and Golden Path suitability for your pull request.

What is a regression contract and when do I need to update it?▼

A regression contract standardizes required test coverage across repositories. You need to update it when new features are developed, using automated feature categorization to determine if the code qualifies for inclusion.

How do I audit QA maturity across multiple code repositories?▼

You can audit QA maturity across repositories by applying this Skill to automate the identification of testing plans, Golden Path suitability, and structured QA decision artifacts for CI/CD gates.

Does this QA automation tool work with existing CI/CD pipelines?▼

Yes, it supports existing CI/CD pipelines by providing structured QA decision artifacts that function as automated gates, ensuring test decisions and regression contracts are enforced before integration.

What is the best way to classify features for automated testing?▼

The best way to classify features for automated testing is through intelligent categorization based on repository type and development stage, which determines the appropriate testing plans and RCI inclusion.

Why does my QA strategy lack consistency across different repositories?▼

Your QA strategy lacks consistency because it lacks a central controller to unify test decisions, regression contracts, and Golden Paths, a problem solved by standardizing cross-repository quality assurance management.