fix-pr-checks

You can automate fixing failing GitHub pull request status checks by orchestrating a single-sweep workflow that diagnoses root causes, applies local code corrections, runs build and test verification, and pushes the changes in one batch.

Yes, resolving CI failures requires authenticated GitHub CLI access and local development environment tools to execute build, lint, and test verification cycles on your repository.

To fix lint and unit test failures in one sweep, the skill delegates log analysis to a subagent to identify the specific file and line, applies the correction, verifies it locally, and pushes the changes.

The best way to diagnose failing PR checks without reading raw logs is using delegated subagent analysis, which processes the logs automatically to identify the root cause of build, lint, test, or snapshot failures.

Yes, you can verify code corrections locally before pushing because the skill automatically runs local build, lint, and test commands to ensure the fixes pass verification before pushing the changes to the pull request.

Automated PR diagnosis can resolve build, lint, test, and snapshot failures by identifying the specific file and line causing the failure, applying the fix, and verifying it locally before pushing.