fix-ci-failures Skill
Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the gh CLI. Published by microsoft in vscode.
Decision snapshot
Is this a fit?
Developers using vscode, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
1 month ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is fix-ci-failures Skill?
Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the gh CLI. Published by microsoft in vscode. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using vscode
Declared skill metadata
- Source file: .github/skills/fix-ci-failures/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use fix-ci-failures Skill
- Use it for developers using vscode.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode
- Skill file: .github/skills/fix-ci-failures/SKILL.md
What it does
Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the gh CLI.
Skill instructions
Investigating and Fixing CI Failures This skill guides you through diagnosing and fixing CI failures on a PR using the gh CLI. The user has the PR branch checked out locally. Workflow Overview 1. Identify the current branch and its PR 2. Check CI status and find failed checks 3. Download logs for failed jobs 4. Extract and understand the failure 5. Fix the issue and push --- Step 1: Identify the Branch and PR bash Get the current branch name git branch --show-current Find the PR for this branch gh pr view --json number,title,url,statusCheckRollup If no PR is found, the user may need to specify the PR number. --- Step 2: Check CI Status bash List all checks and their status (pass/fail/pending) gh pr checks --json name,state,link,bucket Filter to only failed checks gh pr checks --json name,state,link,bucket --jq '.[] | select(.bucket == "fail")' The link field contains the URL to the GitHub Actions job. Extract the run ID from the URL — it's the number after /runs/: https://github.com/mi
Verified compatibility and discovery
Frequently asked questions
What is fix-ci-failures?
fix-ci-failures is a open-source AI agent skill with Copy skill directory. Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause.
Who is fix-ci-failures best for?
fix-ci-failures is best for reusing agent instructions, scripts, and references.
How do I install fix-ci-failures?
Install or run fix-ci-failures using Copy skill directory. Check fix-ci-failures for the latest setup command.
Is fix-ci-failures actively maintained?
fix-ci-failures may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
