What problem does it solve?
Manual management of the full pull‑request lifecycle—branch creation, committing, opening PRs, watching CI, fixing failures, and merging—requires many repetitive commands and context switches.
Core Features & Use Cases
- Branch management: Create and switch to feature branches following conventional naming.
- Commit workflow: Stage changes and create conventional commit messages.
- Pull request creation: Open PRs via the GitHub CLI or, when unavailable, through git plus the GitHub REST API.
- CI monitoring: Check combined status and individual GitHub Actions runs, with optional polling.
- Automatic failure handling: Retrieve logs, diagnose issues, apply fixes, and re‑push until checks succeed.
- Merge options: Perform squash, merge, or rebase merges, and optionally enable auto‑merge.
These capabilities let developers automate the entire PR process in both local and CI‑only environments.
Quick Start
Ask the skill to create a new feature branch, commit your changes, open a pull request, monitor CI, and merge when all checks pass.