Fix ci

Skill motao123/dev-workflow-kit/fix-ci

21 markdown-first software delivery workflow skills for Claude Code, Codex, and compatible agents. Standalone skill kit covering planning, debugging, CI, review, security, rollout, performance, data quality, and post-incident workflows.

Install

npx -y skills add motao123/dev-workflow-kit --skill fix-ci

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

1 stars1 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

Use when CI, build, lint, type-check, or test automation is failing and the branch is blocked. This skill focuses on reading the earliest failure, classifying the failure surface, and choosing the smallest repair that restores pipeline health.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, as published. Nobody here has run it

Fix CI

Use this skill when automation disagrees with local assumptions or blocks integration.

Trigger Conditions

Use this skill when:

CI is red
lint, test, build, or type-check fails in the pipeline
the branch passes locally but fails remotely
logs are noisy and the earliest failure needs to be extracted
the user wants the minimal change that unblocks the pipeline

Do not use this skill for planning-only tasks or for broad product design questions.

Workflow

Read the earliest meaningful failure first.
Classify the failing stage: lint, type, unit test, integration test, build, packaging, environment.
Separate root-cause failure from downstream noise.
Check whether the failure is deterministic, flaky, or environment-specific.
Recommend the smallest repair with the highest confidence.
Re-run the narrowest useful verification.

Output

For non-trivial work, provide:

failing stage
first actionable error
likely cause
minimal repair path
verification to re-run

Coordination

After CI diagnosis:

hand off to the repo's coding workflow for code fixes
use systematic-debugging if root cause is still unclear
use ship-readiness once pipeline health is restored

Invocation Examples

"Use fix-ci to inspect this pipeline failure and find the first actionable error."
"Use fix-ci because local tests pass but CI is still red."
"Use fix-ci and tell me the smallest change that should unblock the branch."