skills.rest
TylerSimons1127
TylerSimons1127COMMUNITY
Explore all skills by this author →
GitHub

github-issue-to-pr

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

Updated Aug 21, 2026
Search Tags:#code review#pull request#github#regression testing#gh cli#CI#issue fixing
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill github-issue-to-pr-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-to-pr
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/github/github-issue-to-pr
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill github-issue-to-pr-tylersimons1127

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, deduplicated, class-complete, and honestly reported. ## 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-Tested Regression Coverage: Temporarily restores old behavior to prove the new regression test actually fails without the fix. - Honest CI Shepherding: Distinguishes diff-introduced failures from baseline or infrastructure flakes and reports only live-verified CI state. - Use Case: A maintainer says "Fix issue #123 and open a PR." The Skill reads the thread, sweeps for duplicates, reproduces the bug, writes a proven regression test, fixes sibling call sites, opens the PR immediately, and monitors CI until the issue is closed with a traceable comment. ## Quick Start Ask the agent to fix GitHub issue number 123 in the current repository and open a verified pull request.

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 fix, then open the PR immediately so CI starts running. Monitor checks until they reflect reality.

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

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

Why verify a regression test fails without the fix?▼

A regression test that passes both with and without the fix proves nothing about the bug. Temporarily restoring the old behavior and confirming the test fails, called a sabotage run, demonstrates the test actually guards the fixed behavior.

Can this workflow handle bugs that are intentional design?▼

Yes. Before implementing, it runs git log -p -S on the targeted code to read the original commit's intent. If the reported bug is deliberate design, the issue premise is challenged instead of blindly changing behavior.

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 carrying an issue from report to verified PR, not for review-only or Q&A tasks.

How are CI failures handled honestly in pull requests?▼

Failures are inspected via gh pr checks and gh run view --log-failed, then classified as introduced by the diff, pre-existing baseline, or infrastructure flakes. Infra flakes get one rerun; green or merged status is never claimed without live evidence.

Related Skills

Explore More Software Engineering Skills→
kieranpottskieranpotts

triage

Verify and classify issue tracker reports, then recommend category and state labels.

Community
Advanced
dimakisdimakis

land-pr

Shepherd GitHub pull requests through CI checks, reviews, and squash merges.

Community
Intermediate
brief-hqbrief-hq
3

development

Enforce Test-Driven Development with the RED-GREEN-REFACTOR cycle and systematic debugging.

Official
Advanced
Maple-and-SpruceMaple-and-Spruce

git-workflow

Standardize Git workflows with branch naming, conventional commits, and PR processes.

Official
Intermediate