project-regression-checklist

Run predefined regression steps and compare outcomes with baselines.

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/hohai99/antigravity-skills --skill project-regression-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-regression-checklist
Source: https://github.com/hohai99/antigravity-skills/tree/main/.agent/skills/project-regression-checklist
Command: npx skills add https://github.com/hohai99/antigravity-skills --skill project-regression-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams verify that project changes do not regress existing functionality by providing a structured regression checklist.

Core Features & Use Cases

  • Automated regression verification: Run a predefined regression suite and compare results against historical baselines.
  • Risk-aware gating: Escalate releases if critical regressions are detected.
  • Use Case: Before shipping a new feature, apply this checklist to ensure no previously fixed bugs have reappeared.

Quick Start

Run the project-regression-checklist after implementing a feature to validate stability and prevent regressive issues.

Frequently Asked Questions about project-regression-checklist

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

FAQPage Schema
How do I automate regression checks before shipping a new feature?

Run regression verification by applying a predefined checklist to compare outcomes against historical baselines. This process validates stability and escalates releases if critical regressions or previously fixed bugs are detected.

What is automated regression verification used for in quality assurance?

Automated regression verification confirms project changes do not break existing functionality by comparing outcomes against baselines. It detects reappeared bugs and escalates releases when critical regressions are found.

When do I need to run a regression suite for post-implementation checks?

Run a regression suite during post-implementation and pre-release contexts to verify new changes do not break existing functionality. This ensures stability by preventing regressive issues before shipping.

Does this regression checklist support risk-aware gating for releases?

Yes, the regression checklist provides risk-aware gating by escalating releases when critical regressions are detected. It compares outcomes with baselines to prevent shipping unstable changes.

How do I generate a regression report after comparing outcomes with baselines?

Generate a regression report by running predefined regression steps and comparing outcomes with historical baselines. The report verifies stability, flags failures, and escalates critical regressions.