github-issue-to-pr

Carry a GitHub issue to a verified pull request with honest CI reporting.

Updated Sep 20, 2026
One-click install
npx skills add https://github.com/GreenyZA/neo-light --skill github-issue-to-pr-greenyza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-to-pr
Source: https://github.com/GreenyZA/neo-light/tree/main/.hermes-home/skills/github/github-issue-to-pr
Command: npx skills add https://github.com/GreenyZA/neo-light --skill github-issue-to-pr-greenyza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a GitHub issue into a merged pull request often fails through skipped steps: unread issue threads, duplicate PRs, fixes that fight intentional design, regression tests that prove nothing, and CI status reported without evidence. This Skill enforces the end-to-end discipline from issue triage to verified CI. ## Core Features & Use Cases - Premise and duplicate validation: Reads the full issue thread, sweeps for existing PRs and recent fixing commits, and checks git history to confirm the reported bug is not deliberate design. - Class-level fixes with proven regression tests: Fixes the same bug shape at sibling call sites and runs a sabotage check confirming the new test fails on pre-fix code. - Honest CI shepherding: Opens the PR immediately to dispatch CI, distinguishes introduced failures from baseline flakes, and closes the loop by commenting the PR link on the issue. - Use Case: Given "Fix issue #123 and open a PR", the Skill reads the thread, reproduces the bug, writes a failing regression test, implements the minimal fix, and reports live CI state. ## Quick Start Ask the agent to fix GitHub issue number 123 in the current repository and open a pull request with verified CI status.

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?▼

Read the full issue thread with gh issue view, sweep for duplicate PRs, reproduce the bug on the current branch, write a failing regression test, implement the minimal fix, then push and open the PR so CI dispatches immediately.

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

Run a sabotage check: temporarily restore the old behavior of the function under test, confirm the new test fails, then restore the fix and confirm it passes. A test that passes both ways proves nothing.

Should I check for duplicate PRs before fixing an issue?▼

Yes. Run gh pr list --search with the issue number plus at least two keyword variants of the symptom, and check recent commits with git log. Popular issues often attract multiple independent fixes, and duplicating wastes the work.

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

Do not use it for reviewing an existing pull request or answering a code question with no requested change. It is designed for carrying an issue through implementation, testing, and CI verification.

Why might a reported bug actually be intentional design?▼

A missing link or restriction is often a deliberate feature. Run git log -p -S on the code the issue wants changed and read the original commit's intent before implementing, so the fix does not fight intentional design.