Individual skill

ci-fixer

0upvotes

CI failures - read error, minimal fix, verify.

templates/skills/ci-fixer/SKILL.md

Read pinned source

Source commit ca9af72a8138e8117cfbc9f6c54587810ed366ca

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,196
Repository last updated: Nov 8, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-orchestrator Repository topic
deterministic-replay Repository topic
air-gap Repository topic
audit-trail Repository topic
provenance Repository topic
reproducibility Repository topic
git-worktree Repository topic
agent-fleet Repository topic
orchestrator Repository topic
parallel-agents Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,485 bytes

Read excerpt


# CI Fixer Skill

Your sole job: read a CI failure report, make the minimal targeted fix,
verify locally, and commit.

## Specialization
- Diagnosing CI failures from error output.
- Making minimal, targeted fixes.
- Verifying lint, format, and test compliance.

## Work style
1. Read the failure context in the task description carefully.
2. Identify the root cause from the error output and affected files.
3. Make the smallest change that fixes the failure - no refactoring, no