# Gait Incident To Regression

> Convert a Gait run artifact into a deterministic regression workflow. Use when asked to initialize fixtures from run_id or runpack path, run graders, produce CI-friendly outputs, or summarize drift and failures. Use when this capability is needed.

- Skill: `tomevault-io/gait-incident-to-regression` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/gait-incident-to-regression`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/gait-incident-to-regression/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/gait-incident-to-regression

---

# Incident To Regression

Execute this workflow to transform an observed run into repeatable CI checks.

## Gait Context

Gait is the offline-first policy-as-code runtime for AI agent tool calls. It enforces tool-boundary policy, emits signed and verifiable evidence artifacts, and supports deterministic regressions.

Use this skill when:
- incident triage needs repeatable fixture creation
- CI gate failures require deterministic grader reruns
- receipt/evidence generation depends on regression outputs

Do not use this skill when:
- Gait CLI is unavailable in the environment
- no Gait run/pack artifact or run identifier is available as input

## Workflow

1. Resolve source run artifact:
   - use `<run_id>` or `<runpack_path>`
2. Initialize fixture deterministically (required):
   - explicit path: `gait capture --from <run_id_or_path> --json`
   - then `gait regress add --from ./gait-out/capture.json --json`
   - legacy fallback: `gait regress init --from <run_id_or_path> --json`
3. Parse and report:
   - `ok`, `run_id`, `fixture_name`, `fixture_dir`, `config_path`, `next_commands`
4. Run regression suite (required):
   - `gait regress run --json`
5. If CI output is requested, add JUnit:
   - `gait regress run --json --junit junit.xml`
6. Return concise summary:
   - source run
   - fixture path
   - pass/fail status
   - failed graders count
   - output paths

## Safety Rules

- Keep replay deterministic defaults.
- For replay workflows, prefer `gait run replay` (stub mode default); require explicit unsafe flags for real tool replay.
- Do not pass `--allow-nondeterministic` unless explicitly requested.
- Treat non-zero regress run exits as regressions, not soft warnings.
- Keep this skill wrapper-only: no inline grading logic and no policy-evaluator behavior outside CLI calls.

## Determinism Rules

- Always create a deterministic fixture before `regress run` for new incidents.
- Always consume `--json` output fields for decisions.
- Keep fixture names stable and explicit when user provides naming constraints.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/clyra-ai) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->