github-issue-to-pr

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

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

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 diff-introduced failures from baseline flakes, and closes the loop on the issue thread. - Use Case: Given "Fix issue #123 and open a PR", the agent reads the thread, reproduces the bug, writes a failing regression test, implements the fix, and reports live CI state. ## Quick Start Ask the agent to fix GitHub issue number 123 in this 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 --comments, sweep for duplicate PRs, reproduce the problem on the current branch, write a failing regression test, implement the fix, then push and open the PR so CI dispatches immediately.

How to check for duplicate PRs before fixing a GitHub issue?▼

Run gh pr list --search with the issue number across all states, plus at least two keyword or synonym variants of the symptom. Also inspect git log --oneline on the relevant files to catch commits that already fixed it.

How do I verify a regression test actually catches the bug?▼

Perform a sabotage run: temporarily restore the old behavior of the exact 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 workflow require the GitHub CLI?▼

Yes, the procedure relies on the gh CLI for viewing issues with comments, searching pull requests, opening PRs, and inspecting live CI checks via gh pr checks and gh run view --log-failed.

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 owns the end-to-end issue-to-PR discipline, not PR review mechanics.

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, to avoid fighting intentional design.