ci-fixer SKILL.md skillA
ci-fixer from hex/claude-council is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hex/claude-council/ci-fixer@git:20260925.093f32aPins git:20260925.093f32a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hex/claude-council
- Path
mods/council-pane/specialists/ci-fixer/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260925.093f32a, committed Sep 25, 2026
- Size
- 3,764 bytes
- Repository stars
- 892
- License
- MIT
A CI job fails on a named revision and the fix belongs in code, config or tests, not in the CI provider.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# CI Fixer Make one failing CI job pass for the right reason. A green run earned by retrying, skipping or loosening a check is a failure of this task, not a success. ## Pin the failure 1. Work from the exact revision SHA, run ID and job named in the task. If the task names only a pull request or a branch, ask for them in the report rather than guessing which run is current. 2. Check that the run is still relevant. A cancelled run is often superseded by a newer run on the same revision or branch. If the newest run passes, stop and report that. 3. Fetch the failed job's log once and keep it. Work from that copy. Prefer the job's own status over a summary or rollup view. 4. Find the first real error, not the last line. Later errors are often consequences. ## Classify before changing anything Put the failure in exactly one class and record the evidence for it: - **product**: the code under test is wrong. The same failure should reproduce locally or in CI's environment. - **test harness**: the test, fixture, helper or setup is wrong, flaky or order-dependent, and the product is fine. - **environment**: runtime version, OS difference, missing tool, dependency …
Read the whole file at its exact version.
How to install
mdr add hex/claude-council/ci-fixer@sha256:732af6fe60ffaddeThe line at the top of this page pins the label git:20260925.093f32a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ezuhp3nh25ufidva)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 25, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3764 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hex/claude-council · 892 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ezuhp3nh25ufidva GET https://markdownregistry.com/api/v1/resolve?ref=hex/claude-council/ci-fixer GET https://markdownregistry.com/api/v1/blob/732af6fe60ffadde0cd99d0cbc51fa684e20150e1a39168de9ec9470aa6db1dd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from hex/claude-council
Every file in hex/claude-council