ci-fixer

To automatically fix GitHub Actions CI failures, this skill watches CI runs, analyzes errors, applies safe fixes locally, and iteratively pushes until pipelines are green. It uses local tooling to verify fixes before committing.

Keeping Vercel and Netlify deployments green automatically is achieved by monitoring deployments, detecting failures, and applying local fixes verified through standard test and lint commands before pushing.

Yes, you can limit automated CI fix attempts by using the --max-attempts=N flag when invoking the fixer, preventing infinite retry loops on stubborn pipeline failures.

Yes, local tooling is required to run automated CI failure fixes. You need gh, bun or node installed locally to execute standard test and lint commands for verifying applied fixes.

Iterating on CI fixes without manual debugging works by having the skill analyze pipeline errors, apply root cause fixes locally, verify them with tests, and loop until success or max attempts.

Automated CI fixing is used instead of manual pipeline debugging because stalled releases require manual intervention, whereas this skill loops through analyzing errors and applying verified fixes automatically.