ci-fix

To auto-fix failing CI runs, you can diagnose and resolve issues directly from your current branch without opening the GitHub Actions UI. The tool classifies failure types like lint, formatting, and lock file issues, then applies safe fixes automatically.

CI failures that can be automatically diagnosed and fixed include lint, formatting, pre-commit, lock file, test, and environment issues. The tool classifies these logs to apply safe fixes or provide actionable recommendations.

You do not strictly need the gh CLI to diagnose GitHub Actions failures, as the tool can fall back to manual log paste if unauthenticated. However, gh CLI is required for the auto-fetch mode to retrieve the latest failed run automatically.

Yes, you can triage CI failures without opening the GitHub Actions UI. The tool auto-fetches the latest failed run on your current branch and generates a concise diagnosis summary to document what happened and what was done.

To resolve pre-commit and lock file issues in your CI pipeline, the tool classifies these specific failure types from the logs and applies safe fixes automatically. It provides structured diagnoses and actionable recommendations to restore the pipeline.

If your CI logs cannot be auto-fetched, you can manually paste the log text into the tool. This fallback mode allows you to diagnose test, lint, and environment failures when the gh CLI is unavailable or unauthenticated.