What problem does it solve? Managing pull requests involves repetitive manual steps across branching, committing, PR creation, CI monitoring, failure diagnosis, and merging, often on machines where the GitHub CLI is unavailable. ## Core Features & Use Cases - Full PR Lifecycle: Create branches with naming conventions, write conventional commits, push, and open PRs using either gh CLI or git plus curl against the GitHub REST and GraphQL APIs. - CI Monitoring and Auto-Fix: Poll check runs and commit statuses, download failed job logs, diagnose failures with a troubleshooting reference, and loop through fix-commit-push cycles up to three attempts. - Merge Automation: Squash, merge, or rebase via API, enable auto-merge through GraphQL, and clean up local and remote branches after merging. - Use Case: After fixing a login redirect bug, the agent creates a fix/login-redirect-bug branch, commits with a conventional message, opens a PR from a template, watches CI, auto-fixes a lint failure, and squash-merges once checks pass. ## Quick Start Create a branch, commit my current changes with a conventional commit message, open a pull request, monitor CI, and merge it when the checks pass.
