How do I install the Fix CI Failures skill?

Run npx skillmds@latest add majiayu000/fix-ci-failures in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fix CI Failures safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fix CI Failures?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fix CI Failures free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fix CI Failures?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fix CI Failures by majiayu000 — Agent Skill

Name: Fix CI Failures
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Fix CI Failures Skill

Diagnose and fix CI failures systematically.

When to Use

CI checks fail on PR
Workflow runs fail
Tests pass locally but fail in CI
Need to debug CI issues

Quick Reference

# View PR checks
gh pr checks <pr-number>

# View specific run details
gh run view <run-id> --log-failed

# Reproduce locally
./scripts/reproduce_ci.sh <run-id>

Workflow

Check status - View failed PR checks
Get logs - Download or view failure details
Reproduce - Run same commands locally
Fix issue - Apply necessary changes
Verify - Test passes locally
Push - Commit and push fix
Monitor - Check CI passes

Common Failures

Failure	Command	Fix
Trailing whitespace	`just pre-commit-all`	Stage and re-commit
Test failure	`pixi run mojo test tests/`	Fix code, re-run tests
Markdown lint	`npx markdownlint-cli2 --fix "*/.md"`	Commit fixes
Build error	Check imports/deps	Update and rebuild

Diagnosis Workflow

# 1. View CI status
gh pr checks 123

# 2. Get failure details
gh run view <run-id> --log-failed

# 3. Download logs for analysis
gh run download <run-id>

# 4. Reproduce issue locally
./scripts/reproduce_ci.sh <run-id>

# 5. Fix the issue
# ... make changes ...

# 6. Verify locally
./scripts/run_ci_locally.sh

# 7. Push fix
git add .
git commit -m "fix: address CI failure"
git push

# 8. Monitor CI
gh pr checks 123 --watch

Error Handling

Error	Cause	Fix
"Cannot find module"	Missing import or broken path	Fix import, check file structure
"Syntax error"	Invalid code	Correct syntax, test compile
"Test failed"	Logic error	Debug test, fix implementation
"Hook failed"	Formatting/whitespace	Run formatters, re-commit

Scripts Available

scripts/get_ci_logs.sh - Download CI logs
scripts/reproduce_ci_failure.sh - Reproduce locally
scripts/run_ci_locally.sh - Run CI checks locally
scripts/fix_common_ci_issues.sh - Auto-fix common issues

Prevention

Run pre-commit before pushing
Run tests locally
Check formatting before commit
Review CI logs regularly

References

Related skill: quality-run-linters for linting
Related skill: run-precommit for pre-commit hooks
Workflow configuration: .github/workflows/

---name: fix-ci-failuresdescription: Diagnose and fix CI/CD failures by analyzing logs, reproducing locally, and applying fixes. Use when CI checks fail on pull requests.--- # Fix CI Failures Skill Diagnose and fix CI failures systematically. ## When to Use - CI checks fail on PR - Workflow runs fail - Tests pass locally but fail in CI - Need to debug CI issues ## Quick Reference ```bash # View PR checks gh pr checks <pr-number> # View specific run details gh run view <run-id> --log-failed # Reproduce locally ./scripts/reproduce_ci.sh <run-id> ``` ## Workflow 1. **Check status** - View failed PR checks 2. **Get logs** - Download or view failure details 3. **Reproduce** - Run same commands locally 4. **Fix issue** - Apply necessary changes 5. **Verify** - Test passes locally 6. **Push** - Commit and push fix 7. **Monitor** - Check CI passes ## Common Failures | Failure | Command | Fix | |---------|---------|-----| | Trailing whitespace | `just pre-commit-all` | Stage and re-commit | | Test failure | `pixi run mojo test tests/` | Fix code, re-run tests | | Markdown lint | `npx markdownlint-cli2 --fix "**/*.md"` | Commit fixes | | Build error | Check imports/deps | Update and rebuild | ## Diagnosis Workflow ```bash # 1. View CI status gh pr checks 123 # 2. Get failure details gh run view <run-id> --log-failed # 3. Download logs for analysis gh run download <run-id> # 4. Reproduce issue locally ./scripts/reproduce_ci.sh <run-id> # 5. Fix the issue # ... make changes ... # 6. Verify locally ./scripts/run_ci_locally.sh # 7. Push fix git add . git commit -m "fix: address CI failure" git push # 8. Monitor CI gh pr checks 123 --watch ``` ## Error Handling | Error | Cause | Fix | |-------|-------|-----| | "Cannot find module" | Missing import or broken path | Fix import, check file structure | | "Syntax error" | Invalid code | Correct syntax, test compile | | "Test failed" | Logic error | Debug test, fix implementation | | "Hook failed" | Formatting/whitespace | Run formatters, re-commit | ## Scripts Available - `scripts/get_ci_logs.sh` - Download CI logs - `scripts/reproduce_ci_failure.sh` - Reproduce locally - `scripts/run_ci_locally.sh` - Run CI checks locally - `scripts/fix_common_ci_issues.sh` - Auto-fix common issues ## Prevention - Run pre-commit before pushing - Run tests locally - Check formatting before commit - Review CI logs regularly ## References - Related skill: `quality-run-linters` for linting - Related skill: `run-precommit` for pre-commit hooks - Workflow configuration: `.github/workflows/`

Frequently asked questions

Fix CI Failures