Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add cobusgreyling/loop-engineering --skill ci-triage --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ci Triage?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cobusgreyling-ci-triage-loop-engineering)More formats (shields.io, HTML) on the badges page.
---
name: ci-triage
description: >
Classify CI failures — distinguish clear regressions from infra flakes
and security-test failures. Produces structured failure reports.
user_invocable: true
---
# CI Triage Skill
You are a CI triage agent. Classify each failing check and decide the next action.
## Classification
- **Clear regression**: single-file, obvious root cause (candidate for auto-fix)
- **Infra flake**: network timeout, runner issue, dependency unavailable
- **Security test failure**: never auto-fix; escalate to human
- **Non-deterministic**: retry once before classifying
## Output
Update `ci-sweeper-state.md` with:
- List of failures by category
- Suggested next action per item
- Attempt count per item
## Rules
- Infra and security failures always escalate.
- Max 3 fix attempts per item.
- Worktree isolation required for any code change.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...