Skip to content

Add incident-to-regression, CI triage, and evidence receipt skills#168

Open
davidahmann wants to merge 3 commits intoopenai:mainfrom
davidahmann:dah/add-gait-portable-skills
Open

Add incident-to-regression, CI triage, and evidence receipt skills#168
davidahmann wants to merge 3 commits intoopenai:mainfrom
davidahmann:dah/add-gait-portable-skills

Conversation

@davidahmann
Copy link

Summary

Adds three portable skill entries under skills/.curated:

  • incident-to-regression
  • ci-failure-triage
  • evidence-receipt-generation

Design goals

  • generic workflows without repo-locked assumptions
  • deterministic command-driven behavior
  • concise usage and validation examples with expected output
  • clear handoff/evidence posture for CI and incident workflows

Notes

These entries were generated from shared core skill content and adjusted for OpenAI/Codex invocation wording.

@davidahmann davidahmann requested a review from a team February 15, 2026 17:04
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3ec65ca05e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

1. Verify the failing artifact first:
- `gait verify <failure_target> --json`
2. If failure came from regress grading, rerun deterministically:
- `gait regress run --json`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Bind regress reruns to the failing target

Step 2 reruns gait regress run --json without ever using failure_target, so in any workspace that already has a different fixture/config selected, triage can report the wrong run's result instead of the failing artifact the user asked to investigate. This breaks root-cause isolation because the workflow's key input is effectively ignored during the rerun path.

Useful? React with 👍 / 👎.

## Workflow

1. Initialize deterministic fixture from the incident source:
- `gait regress init --from <run_source> --json`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Honor the declared workdir before generating fixtures

The skill declares workdir as a required input for where fixtures/outputs should be created, but the workflow never changes into that directory or passes it to gait regress init. As written, artifacts are created in whatever the current shell directory happens to be, which makes output paths nondeterministic and can pollute unrelated repos.

Useful? React with 👍 / 👎.

1. Verify integrity before receipt generation:
- `gait verify <source> --json`
2. Generate receipt from source artifact:
- `gait run receipt --from <source> --json`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Wire out_path into receipt generation

The inputs section advertises out_path as the destination file for JSON receipt output, but the workflow command only prints to stdout and never uses that parameter. In automation contexts this causes missing receipt files unless callers add undocumented shell redirection, which contradicts the declared interface.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant