Verified:GitHub

gait-incident-to-regression

Converts GitLab incident run artifacts into deterministic regression workflows with CI-friendly outputs.

12|5|Updated Feb 5, 2026

Search Tags:#regression #fixtures #reproducibility #ci #incident #gait #graders

One-click install

npx skills add https://github.com/Clyra-AI/gait --skill gait-incident-to-regression-clyra-ai

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gait-incident-to-regression
Source: https://github.com/Clyra-AI/gait/tree/main/.agents/skills/gait-incident-to-regression
Command: npx skills add https://github.com/Clyra-AI/gait --skill gait-incident-to-regression-clyra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert observed Gait run artifacts into repeatable CI-ready regression checks, reducing manual fixture recreation and enabling reproducible evaluations.

Core Features & Use Cases

Deterministic fixture initialization: takes a run_id or runpack to recreate fixtures identically.
Deterministic regression execution: runs graders and produces structured outputs suitable for CI (JUnit if requested).
Audit-ready summaries: returns concise status summaries with source details and artifact paths for reporting.

Quick Start

Initialize deterministic regression fixtures from a run_id or runpack path and run the regression suite to produce CI-friendly outputs.

Frequently Asked Questions about gait-incident-to-regression

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

FAQPage Schema

How do I create deterministic regression fixtures from a run artifact?▼

To create deterministic regression fixtures, initialize them directly from a specific run_id or runpack path. This recreates the exact conditions of the original run, ensuring reproducible evaluations without manual fixture recreation.

Can I generate JUnit reports for CI from regression runs?▼

Yes, you can generate CI-friendly outputs including optional JUnit reports. Running graders during the deterministic regression execution phase produces structured test results suitable for integration pipelines.

What is the required workflow for running graders on a Gait incident?▼

The required workflow mandates a sequential process: you must execute the regress init step to initialize fixtures before running regress run. This ensures deterministic replay of the incident for accurate grader evaluation.

How do I summarize drift and failures from regression checks?▼

Summarizing drift and failures is handled automatically by the regression workflow. It produces audit-ready status summaries containing source details and artifact paths for concise reporting.

Do I need a runpack path to initialize a regression workflow?▼

You need either a run_id or a runpack path to initialize the regression workflow. Providing one of these inputs allows the system to deterministically recreate the necessary fixtures from the observed run.

Why are my regression checks failing to replay deterministically?▼

Regression checks fail to replay deterministically if the regress init step is skipped before regress run. You must initialize fixtures directly from a run_id or runpack path to enforce deterministic execution.