skills.rest
LanternOps
LanternOpsOFFICIAL
Explore all skills by this author →
GitHub

issue-to-pr

Automate a GitHub issue from claim to reviewed open PR.

73|23|Updated Jan 14, 2026
Search Tags:#automation#workflow#github#verification#worktree#issue#pr
One-click install
npx skills add https://github.com/LanternOps/breeze --skill issue-to-pr-lanternops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-to-pr
Source: https://github.com/LanternOps/breeze/tree/main/.claude/skills/issue-to-pr
Command: npx skills add https://github.com/LanternOps/breeze --skill issue-to-pr-lanternops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates carrying a chosen GitHub issue from claim to a reviewed, open PR, ensuring a structured, auditable workflow without merging or closing the issue by the worker.

Core Features & Use Cases

  • Carries a single pre-chosen GitHub issue through claim, isolated worktree setup, patching, verification, and PR creation.
  • Enforces governance: the worker never merges or closes the issue; human decision is required for final merge.
  • Applicable after triage (gh-queue) to execute a defined lifecycle, including checks and reviews before PR readiness.

Quick Start

Provide the issue number to begin the end-to-end claim-to-PR workflow and watch it progress through verification and review.

Frequently Asked Questions about issue-to-pr

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

FAQPage Schema
How do I automate a GitHub issue to PR workflow end-to-end?▼

You can automate a GitHub issue to PR workflow by providing an explicit issue number. The workflow then carries the issue through claim, isolated worktree setup, patching, verification, and PR creation automatically.

What is an isolated worktree and how does it help with GitHub issue automation?▼

An isolated worktree in GitHub issue automation provides a separate Git working directory for patching and verification. It ensures the fix is applied and tested independently before PR creation, maintaining a structured and auditable workflow.

Do I need an issue number to start the GitHub claim to PR workflow?▼

Yes, an explicit issue number is required to start the GitHub claim to PR workflow. The automation relies on this specific identifier to claim the issue, apply the fix, run verification, and prepare the PR.

Does the issue to PR automation merge or close the original GitHub issue?▼

No, the issue to PR automation never merges or closes the original GitHub issue. It enforces governance by requiring human decision for the final merge, leaving the issue open while preparing the PR.

Can I use this workflow automation after GitHub issue triage?▼

Yes, you can use this workflow automation after GitHub issue triage. It is designed to execute the defined lifecycle steps, including checks and reviews, immediately following triage decisions to reach PR readiness.

What are the limitations of automating GitHub issue resolution with worktrees?▼

A limitation of automating GitHub issue resolution with worktrees is that it relies on git tooling and PR automation conventions to enforce guardrails. It strictly handles a single pre-chosen issue per run and cannot perform the final merge.

Related Skills

vultukvultuk
1

fix-github-issue

Plan, implement, and submit a GitHub issue fix via a dedicated git worktree.

Community
Advanced
nbramianbramia
20

implement

Coordinate end-to-end implementation workflows from issue understanding through PR merge.

Community
Advanced
stevengonsalvezstevengonsalvez

gh-issue

Guide GitHub issue triage, root-cause analysis, and PR-ready patch creation.

Community
Intermediate
jellydnjellydn
114

pr-review

Apply GitHub PR review comments as code edits and commits.

Community
Intermediate