skills.rest
hujianbest
hujianbestCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

hf-regression-gate

Collect fresh evidence and produce a regression gate verdict after traceability review.

1|Updated Mar 22, 2026
Search Tags:#testing#verification#build#worktree#evidence#regression#gate
One-click install
npx skills add https://github.com/hujianbest/garage-agent --skill hf-regression-gate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hf-regression-gate
Source: https://github.com/hujianbest/garage-agent/tree/main/packs/coding/skills/hf-regression-gate
Command: npx skills add https://github.com/hujianbest/garage-agent --skill hf-regression-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a traceability review, this skill provides a regression verification gate to ensure changes do not destabilize related modules and that the appropriate regression checks are performed. It is not intended to decide task completion, finalize work, or route when requirements are unclear.

Core Features & Use Cases

  • Defines regression scope based on traceability outcomes (full / standard / lightweight) and aligns validation effort with risk.
  • Guides the collection of fresh evidence across code, tests, and build results to support a defensible gate decision.
  • Delivers a clear verdict and a recommended next action or routing path (e.g., proceed to completion gate, or route to workflow-router).

Quick Start

After you complete a traceability review, run the regression gate to collect fresh evidence and determine the gate outcome.

Frequently Asked Questions about hf-regression-gate

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

FAQPage Schema
How do I set up a regression gate to prevent upstream changes from breaking downstream modules?▼

A regression gate verifies regression health by collecting fresh evidence across code, tests, and builds after upstream changes, ensuring downstream modules do not break. It evaluates verification scope and outputs a clear pass or fail verdict.

What is the difference between full, standard, and lightweight regression scope?▼

Regression scope levels (full, standard, lightweight) define the validation effort applied during the gate check, aligning testing depth with risk based on traceability outcomes to ensure appropriate verification coverage.

When do I need to collect fresh evidence for a regression check?▼

You need to collect fresh evidence for a regression check when a formal gate is requested after a traceability review. This ensures the gate decision is defensible and based on current code, test, and build results rather than stale data.

Can I use a regression gate to finalize tasks or route workflows when requirements are unclear?▼

No, this regression gate is not intended for task completion, finalization, or workflow routing when requirements are unclear. It strictly verifies regression health and produces a next action, such as proceeding to a completion gate or routing to a workflow router.

What type of evidence is required to pass a formal regression verification gate?▼

A formal regression verification gate requires fresh evidence collected across code, tests, and build results. This evidence supports a defensible gate decision by proving the changes have not destabilized related modules.

Related Skills

Explore More Software Engineering Skills→
SSiertsemaSSiertsema

impact-analysis

Analyze proposed changes across a traceability graph to identify affected artifacts and risks.

Community
Advanced
voodootikigodvoodootikigod
16

adlc

Route software work through ADLC gates P1-P7 using Codex CLIs.

Community
Advanced
miyamo2miyamo2

kiro-verify-completion

Verify completion claims using canonical validation commands and fresh outputs.

Community
Advanced
shynlee04shynlee04

idumb-validation

Validate iDumb plugin components through pivotal trials and stress testing.

Community
Advanced