What problem does it solve? Managing pull requests involves repetitive manual steps across branching, committing, PR creation, CI monitoring, failure diagnosis, and merging, often requiring different tooling depending on whether the GitHub CLI is installed. ## Core Features & Use Cases - Full PR Lifecycle Automation: Create branches with conventional naming, write Conventional Commits messages, push, and open PRs using either the gh CLI or git plus curl against the GitHub REST API. - CI Monitoring and Auto-Fix Loop: Poll commit statuses and check runs, download failed workflow logs, diagnose failures using a troubleshooting reference, patch code, and re-push until checks pass. - Merge Management: Squash, rebase, or merge-commit PRs, enable auto-merge via the GraphQL API, and clean up local and remote branches after merging. - Use Case: After fixing a login bug, an agent creates a fix/login-redirect-bug branch, commits with a conventional message, opens a PR that closes the linked issue, watches CI, auto-fixes a failing lint check, and squash-merges once green. ## Quick Start Ask the agent to create a branch, commit your current changes, open a pull request, monitor CI, and merge it when all checks pass.