PluginBench
Skill
Review
Audit score 70

fix-ci

cursor/plugins

Diagnose and fix failing PR checks with iterative, focused solutions.

What is fix-ci?

Automates the process of identifying failing CI checks in pull requests, extracting root causes from logs, and applying targeted fixes. Use this when your PR checks are failing and you need a systematic way to iterate toward green status.

  • Resolves active PR and inspects check status via `gh pr checks`
  • Extracts actionable errors from GitHub Actions logs or external check links
  • Applies minimal, low-risk fixes one failure at a time
  • Re-checks PR status after each fix and repeats until all checks pass
  • Maintains iteration history showing fixes applied in order

How to install fix-ci

npx skills add https://github.com/cursor/plugins --skill fix-ci
Prerequisites
  • GitHub CLI (`gh`) installed and authenticated
  • Active pull request with failing checks
  • Access to PR logs and check details
Claude Code
Cursor
Windsurf
Cline

How to use fix-ci

  1. 1.Trigger the skill when a PR has failing checks
  2. 2.Review the identified primary failing job and root error
  3. 3.Examine the suggested minimal fix
  4. 4.Allow the skill to apply the fix and push changes
  5. 5.Check the updated CI status in the output
  6. 6.Repeat for remaining failures until all checks pass

Use cases

Good for
  • Quickly resolve failing CI pipelines during active development
  • Debug and fix test failures, linting errors, or build issues in PRs
  • Identify root causes from CI logs when checks fail on external services
  • Iterate through multiple CI failures systematically without manual log inspection
  • Unblock PR merges by applying focused fixes to the first actionable error
Who it's for
  • Developers working on pull requests with failing checks
  • CI/CD engineers debugging pipeline failures
  • Teams using GitHub Actions for continuous integration
  • Anyone needing faster iteration on broken builds or tests

fix-ci FAQ

What if the error message is unclear or not actionable?

The skill extracts the first actionable error from logs. If logs are insufficient, it uses the external check link to identify the failing command or service. You can inspect the link directly for more context.

Does this skill make broad refactors or only minimal fixes?

It applies the smallest safe fix first. Broader refactors are avoided in favor of low-risk, targeted changes to unblock the PR.

How does it know when to stop iterating?

It uses `gh pr checks` as the source of truth. Once all checks show a passing state, iteration stops and the PR is ready.

Can it fix checks from external services?

Yes. When GitHub Actions logs aren't available, it uses the check link to identify the failing command or service and applies fixes accordingly.

What if multiple checks are failing?

It fixes one actionable failure at a time, re-checks after each fix, and repeats until all checks pass.

Full instructions (SKILL.md)

Source of truth, from cursor/plugins.


name: fix-ci description: Find failing PR checks, inspect logs or external check links, and apply focused fixes

Fix CI

Trigger

Branch or PR CI is failing and needs a fast, iterative path to green checks.

Workflow

  1. Resolve the active PR and inspect gh pr checks --json name,bucket,state,workflow,link.
  2. Inspect failed jobs and extract the first actionable error. Use GitHub Actions logs when available; otherwise use the check link to identify the failing command or service.
  3. Apply the smallest safe fix.
  4. Push, re-check the PR check set, and repeat until green.

Guardrails

  • Fix one actionable failure at a time.
  • Prefer minimal, low-risk changes before broader refactors.
  • Keep gh pr checks as the source of truth for overall PR CI state.

Output

  • Primary failing job and root error
  • Fixes applied in iteration order
  • Current CI status and next action