ci-fixer

To automatically fix GitHub Actions failures, ci-fixer monitors CI runs in real time, diagnoses errors, and applies verified fixes locally by running tests and linting before committing and pushing to retrigger CI.

Yes, you can automatically loop CI fixes for Vercel and Netlify deployments. The skill watches pipelines, applies local fixes, and pushes changes to retrigger CI until the pipeline is green.

You can limit automated CI fix attempts by using the max-attempts flag, such as /ci-fixer --max-attempts=3, to define the maximum number of fix loops the skill will execute before stopping.

The best way to ensure local fixes pass CI is to enforce local tests and linting before committing. The skill verifies changes locally, commits proper fixes, and saves artifacts for traceability before pushing.

Automated CI fixing works without a maximum attempt limit by continuously looping until the pipeline is green, though setting a limit using the max-attempts flag is recommended to prevent excessive runs.