regression-cicd-hooks

Integrate automated regression testing into GitHub Actions, GitLab CI, and Gitea Actions pipelines.

175|26|Updated Aug 14, 2025

Search Tags:#automation #testing #ci/cd #github actions #regression testing #gitlab ci #gitea actions

One-click install

npx skills add https://github.com/jmagly/aiwg --skill regression-cicd-hooks-jmagly

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: regression-cicd-hooks
Source: https://github.com/jmagly/aiwg/tree/main/plugins/sdlc/skills/regression-cicd-hooks
Command: npx skills add https://github.com/jmagly/aiwg --skill regression-cicd-hooks-jmagly

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the integration of regression testing into your Continuous Integration and Continuous Deployment (CI/CD) pipelines, preventing regressions from reaching production.

Core Features & Use Cases

Automated Baseline Comparison: Compares current test results against established baselines.
Merge Blocking: Prevents merging of code that introduces regressions.
Multi-Platform Support: Integrates with GitHub Actions, GitLab CI, and Gitea Actions.
Pre-Commit Hooks: Catches common regression patterns locally before committing.
Notifications: Alerts teams about detected regressions.
Use Case: Ensure that every pull request automatically runs regression tests. If any tests fail or performance degrades beyond a defined threshold, the merge is blocked, and the team is notified with a detailed report.

Quick Start

Add regression checks to your CI pipeline by running the command "setup regression pipeline".

Frequently Asked Questions about regression-cicd-hooks

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

FAQPage Schema

How do I automate regression testing in GitHub Actions and GitLab CI pipelines?▼

Automated regression testing in CI/CD pipelines is achieved by integrating baseline comparison checks that trigger on pull requests. This Skill supports GitHub Actions, GitLab CI, and Gitea Actions to run tests, compare results against established baselines, and block merges if regressions are detected.

How do I block pull request merges when regression tests fail?▼

To block pull request merges when regression tests fail, you enforce merge blocking within your CI/CD pipeline. This Skill evaluates automated baseline comparisons and prevents code merging if regressions are found, subsequently alerting the team with detailed reports.

Can I catch regressions locally before committing code to my CI pipeline?▼

Yes, you can catch regressions locally before committing code by implementing pre-commit hooks. This Skill provides pre-commit hook implementations that identify common regression patterns before changes are submitted to the remote repository.

How do I manage regression test baselines across multiple environments?▼

Managing regression test baselines across multiple environments is handled through multi-environment baseline management. This Skill automates the tracking and comparison of these baselines to ensure reproducible and auditable AI-augmented development workflows.

Does this regression testing automation work with Gitea Actions?▼

Yes, this regression testing automation works with Gitea Actions, alongside GitHub Actions and GitLab CI. It provides multi-platform support to integrate baseline comparison, merge blocking, and team notifications across these specific CI/CD platforms.