github-pr-workflow

Automates the full GitHub pull request lifecycle from branch creation through CI monitoring and merge.

14|5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill github-pr-workflow-mlt-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/MLT-OSS/hermes-agent-go/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill github-pr-workflow-mlt-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing pull requests involves many repetitive steps—creating branches, writing conventional commits, opening PRs, watching CI, diagnosing failures, and merging—and doing them manually or inconsistently slows down development and introduces errors. ## Core Features & Use Cases - End-to-End PR Lifecycle: Create branches with naming conventions, commit with Conventional Commits format, push, and open PRs with structured body templates for features and bugfixes. - Dual Auth Modes: Uses the gh CLI when available and automatically falls back to git plus the GitHub REST API via curl with a GITHUB_TOKEN on machines without gh. - CI Monitoring and Auto-Fix: Poll check runs and commit statuses, download failed job logs, diagnose common failure patterns (tests, lint, types, build, permissions, timeouts), apply fixes, and re-verify—up to 3 attempts before escalating. - 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 referencing the issue, watches CI, fixes a failing lint check, and squash-merges once green. ## Quick Start Create a pull request for my current changes, monitor the CI checks, fix any failures, and merge it when everything passes.

Frequently Asked Questions about github-pr-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub pull request from the command line?

Use `gh pr create` with a title and body if the GitHub CLI is installed, or send a POST request to the GitHub REST API pulls endpoint with your branch as head and main as base. Both approaches are covered with full command examples.

How to monitor GitHub CI checks and auto-fix failures?

Run `gh pr checks --watch` or poll the commit status API endpoint until checks complete. On failure, download the run logs, match the error against common patterns like test, lint, or build failures, apply a fix, push, and re-check.

Can I create PRs without the gh CLI installed?

Yes, every operation has a fallback using git plus curl against the GitHub REST API with a GITHUB_TOKEN. The token can be read from the environment, a ~/.hermes/.env file, or git credentials.

Does this support squash merge and auto-merge?

Yes, squash merge works via `gh pr merge --squash --delete-branch` or the REST merge endpoint with merge_method set to squash. Auto-merge requires the GraphQL API since REST does not support it, and the repo must have auto-merge enabled.

Why does my CI keep failing after pushing fixes?

Common causes include assertion mismatches in tests, missing dependencies, lint violations, type errors, or permission issues with workflow tokens. The troubleshooting reference maps log signatures to diagnoses and fixes for each failure category.