pr-autopilot

To automate PR CI failure fixes, use this Skill to diagnose failing tests locally, distinguish flaky tests from genuine failures, and push remediation changes directly to GitHub. It processes AI review comments and generates unit tests aligned with your repository patterns.

Yes, you can automatically generate unit tests to close coverage gaps. The Skill analyzes your repository conventions and patterns to produce tests that fit your project, running them locally to verify they resolve the CI failures before pushing fixes.

The best way to handle flaky tests blocking a PR is to run them locally through the Skill, which distinguishes flaky behavior from genuine code failures. It safely diagnoses the test environment and applies fixes or exemptions based on your project conventions.

Yes, you need local repo access and the GitHub CLI to automate PR remediation. The Skill requires local repository access to run tests, diagnose failures, and apply changes safely, while the GitHub CLI interfaces with your pull requests and CI workflows.

Automated PR remediation aligns with existing project conventions by analyzing your repository patterns before generating fixes or unit tests. The Skill coordinates with your established codebase structure to ensure proposed changes match your project's specific coding standards.

Automated CI failure diagnosis requires knowledge of project conventions to safely apply changes without breaking existing patterns. The Skill uses this context to generate unit tests and propose fixes that align with your repository's specific architecture and testing frameworks.