Ci fix

Reusable agent skills for real repository work: review, implementation, release, documentation, and project hygiene.

Install

npx -y skills add bakerstreetco/skills --skill ci-fix

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Diagnose and repair failing CI checks with the smallest safe change. Use when asked to fix GitHub Actions, GitLab CI, local test failures, lint failures, typecheck failures, build failures, or release pipeline errors.

SKILL.md

1.5 KB, as published. Nobody here has run it

CI Fix

Use this skill to turn a failing check into a reproduced diagnosis and a minimal fix. Prefer the exact failing command and logs over guessing.

Workflow

Identify the failing check, command, job, branch, and commit.
Collect logs from the local terminal, CI output, or hosting CLI when available.
Reproduce locally with the closest focused command before changing code when practical.
Classify the failure: code regression, test expectation, environment drift, dependency issue, flaky timing, missing generated file, or configuration problem.
Implement the smallest fix that addresses the root cause.
Re-run the failing command and one adjacent safety check when practical.
Avoid hiding failures by weakening tests or disabling checks unless that is the intended fix and the reason is documented.

Common Commands

git status --short --branch
gh run list --limit 10
gh run view --log
npm test
npm run lint
pytest
go test ./...
cargo test

Use the commands that match the repo; do not assume a package manager without checking.

Output

Summarize:

Failing check and root cause.
Files changed.
Verification commands and results.
Any remaining CI-only risk that could not be reproduced locally.

Gives 0 of the 12 instructions most ci cd skills give

Counted across 392 of the 394 authors here whose files we hold, read 2026-08-06

pin third-party actions to full commit SHAsin 33 of 392
cache dependencies appropriatelyin 24 of 392, across 12 files
optimize pipelines exceeding ten minutesin 20 of 392, across 6 files
enforce all quality gates before mergein 20 of 392, across 7 files
Configure branch protection rulesin 19 of 392, across 5 files
use environments for deployment trackingin 19 of 392, across 7 files
implement manual gates for productionin 19 of 392, across 7 files
implement security scanningin 18 of 392, across 5 files
fix failing code instead of disabling checksin 18 of 392, across 4 files
use CI/CD variables for secretsin 18 of 392, across 6 files
move checks upstream in the pipelinein 17 of 392, across 3 files
use specific image tagsin 17 of 392, across 5 files

Said here and by no other author read

identify the failing check, command, branch, and commit
collect logs from local terminal, CI, or hosting CLI
reproduce locally with the closest focused command
implement the smallest root cause fix
re-run the failing command and one adjacent check
use commands that match the repository

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.