regression

Automates tiered regression testing across modules and integrates with CI workflows.

3|Updated May 28, 2026

Search Tags:#automation #testing #regression #quality-assurance #ci #test-strategy

Ready to run

npx skills add https://github.com/mahg-es/araya --skill regression-mahg-es

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: regression
Source: https://github.com/mahg-es/araya/tree/main/skills/regression
Command: npx skills add https://github.com/mahg-es/araya --skill regression-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regression testing ensures existing functionality remains stable after changes by automatically running suites and guarding against regressions.

Core Features & Use Cases

Inventory and categorize tests by module to identify coverage gaps
Define regression tiers (Smoke, Core, Full) and align CI runs
Map dependencies and generate regression coverage for production bugs
Integrate with CI to run targeted tests on commits, PRs, and releases

Quick Start

Configure regression planning for your project and integrate it into CI to trigger smoke tests on every commit.

Frequently Asked Questions about regression

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

FAQPage Schema

How do I automate regression tests for multi-module projects?▼

Automate regression tests by inventorying and categorizing tests by module, defining tiered test execution, and integrating the suites into your CI pipeline to trigger targeted runs on commits. This ensures existing functionality remains stable after changes.

What are regression testing tiers and how do they align with CI runs?▼

Regression testing tiers are categorized test execution levels like Smoke, Core, and Full. They align with CI runs by triggering targeted tests on commits, PRs, and releases, ensuring rapid feedback while managing overall test suite coverage.

How do I add regression coverage for production bugs?▼

Add regression coverage for production bugs by mapping dependencies, tagging the associated tests, and integrating them into the appropriate CI regression tier. This ensures the same bug is automatically caught in future commits.

Can I integrate smoke tests to run on every commit?▼

Yes, you can integrate smoke tests to run on every commit. By configuring regression planning and defining tiered test execution, the CI pipeline automatically triggers the smoke test suite on each commit to quickly validate changes.

What is the best way to identify regression test coverage gaps?▼

The best way to identify regression test coverage gaps is to inventory and categorize tests by module. This process highlights untested areas and helps map dependencies to ensure comprehensive regression coverage across the project.