github-issue-to-pr

Convert GitHub issues into tested pull requests with verified CI state.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill github-issue-to-pr-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-to-pr
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/skills/github/github-issue-to-pr
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill github-issue-to-pr-vivekgoquest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a GitHub issue into a merged pull request involves many failure points: stale issue threads, duplicate PRs from other contributors, misdiagnosed root causes, regression tests that prove nothing, and premature claims of green CI. This Skill enforces an end-to-end discipline so every fix is validated against current code, proven by a failing-then-passing test, and reported with honest CI evidence. ## Core Features & Use Cases - Premise Validation: Reads the full issue thread and git history to confirm the reported bug is real and not intentional design before writing code. - Duplicate and Class-Level Sweeps: Searches existing PRs and sibling call sites so work is not duplicated and the whole bug class is fixed in one PR. - Sabotage-Run Test Verification: Temporarily restores old behavior to prove the regression test actually fails without the fix. - Honest CI Shepherding: Inspects live check logs, distinguishes diff-introduced failures from baseline flakes, and closes the loop on the issue thread. - Use Case: A maintainer says "Fix issue #123 and open a PR." The Skill reads the thread, reproduces the bug, writes a regression test, implements the fix, opens the PR, and monitors CI to completion. ## Quick Start Ask the agent to fix GitHub issue number 123 in the current repository and open a pull request with verified CI.

Frequently Asked Questions about github-issue-to-pr

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

FAQPage Schema
How do I turn a GitHub issue into a pull request automatically?▼

Read the full issue thread with gh issue view, reproduce the bug on the current branch, write a failing regression test, implement the minimal fix, then push and open the PR with gh. The Skill automates this sequence including CI monitoring.

How to verify a regression test actually catches the bug?▼

Use a sabotage run: temporarily restore the pre-fix behavior of the function under test, run the new test, and confirm it fails. Then restore the fix and confirm it passes. A test passing both ways proves nothing.

Does this work with the GitHub CLI on Windows and macOS?▼

Yes, the Skill declares support for linux, macos, and windows platforms. It relies on the gh CLI commands like gh issue view, gh pr list, and gh pr checks, which work across all three operating systems.

When should I not use an issue-to-PR workflow?▼

Do not use it for reviewing an existing pull request or answering code questions with no requested change. It is designed for issues that demand a code modification carried through to a verified PR.

Why check git history before fixing a reported bug?▼

Running git log -p -S on the target code reveals the original commit's intent. A reported bug is often deliberate design, and implementing the issue blindly can fight intentional restrictions or behavior.