Fix Ci
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.
Install
$ agentstack add skill-motao123-dev-workflow-kit-fix-ci ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-motao123-dev-workflow-kit-fix-ci) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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-debuggingif root cause is still unclear - use
ship-readinessonce 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."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: motao123
- Source: motao123/dev-workflow-kit
- License: MIT
- Homepage: https://motao123.github.io/dev-workflow-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.