github-pr-workflow

Automating a GitHub pull request workflow involves creating branches, committing with conventional commit messages, opening PRs via `gh`, monitoring CI checks, and merging once green. This Skill orchestrates that entire lifecycle end-to-end.

Fixing failing CI checks requires pulling failed workflow logs, inspecting the error, applying code changes, and re-pushing until checks pass. This Skill automates log-driven remediation by fetching workflow run logs and applying fixes iteratively.

Creating and monitoring GitHub PRs without `gh` uses a `git` and `curl` fallback that calls the GitHub REST API directly. This requires authenticated token-based access to manage pull requests, checks, and merges.

Squash merges can be enabled automatically when CI passes by using `gh` or the GitHub REST API. This Skill supports squash merge strategies and optional auto-merge enablement for passing pull requests.

Conventional commit messages provide consistent Git practices across feature and fix branches, ensuring clear history during automated PR workflows. This Skill applies them automatically when committing and pushing changes.

This workflow supports auto-fixing CI failures in Git repositories with GitHub remotes, requiring authenticated GitHub access. It pulls failed workflow logs, applies code changes, and re-checks until CI is green.