ci-triage
FeaturedParse CI failures, identify failing job/step, classify as flake, regression, env, or config. Use in CI sweeper loops before any fix attempt.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- cobusgreyling
- Repository
- cobusgreyling/loop-engineering
- Created
- 1 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
ci-sweeper
Triage failing CI on integration branches and/or PR heads, classify failures, apply minimal fixes when actionable. Use when the user asks to triage or fix CI failures, when automation detects failed workflow runs, or when automation supplies detection JSON. Default is survey only; edit files only when the user explicitly requests a fix or automation sets may_edit in Constraints.
ci-failure-triage
Triage a CI / PR check failure by READING the failure body before forming any hypothesis. Triggered whenever a required check is red, a PR is BLOCKED, a merge won't land, or you're about to call a failure "transient", "flaky", "stale", or "orphaned". Prevents dismissing a real failure (e.g. real CodeQL security alerts) as noise.
failure-triage
Classify failures before changing implementation. Use after failed builds, tests, commands, or smoke checks.