skills.rest
sethdavis512
sethdavis512COMMUNITY
Explore all skills by this author →
Website𝕏@sethdavis512GitHub

github-issue-to-pr

Implements a GitHub issue and opens a linked pull request with validation and screenshots.

4|Updated Oct 24, 2025
Search Tags:#automation#pull request#github#playwright#e2e testing#gh cli#issue
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill github-issue-to-pr-sethdavis512
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-to-pr
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/github-issue-to-pr
Command: npx skills add https://github.com/sethdavis512/iridium --skill github-issue-to-pr-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a GitHub issue into a reviewable pull request involves many manual steps: fetching issue context, creating a linked branch, implementing the change, running tests, capturing UI screenshots, and writing a proper PR body. This Skill automates that entire workflow end to end. ## Core Features & Use Cases - Issue intake and branch setup: Fetches the issue with the gh CLI, self-assigns it, and creates a linked branch via gh issue develop. - Validated implementation: Runs typecheck, lint, unit tests, and targeted Playwright e2e specs until green, adding e2e coverage for new user-visible behavior. - Visual documentation: Captures themed, hydrated screenshots of changed UI surfaces and links them in the PR body. - Use Case: A maintainer says "work on issue #123" and receives an open PR with a conventional commit, a Fixes #123 closing reference, test results, and embedded screenshots of the changed pages. ## Quick Start Ask the assistant to work on issue #123 and take it to a 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 automatically?▼

Provide the issue number or paste the github.com issue URL. The workflow fetches the issue with gh, self-assigns it, creates a linked branch via gh issue develop, implements the change, validates it, and opens a PR with a Fixes # reference.

How does gh issue develop link a branch to an issue?▼

gh issue develop <number> --base main --checkout generates a branch name from the issue title and registers it as a GitHub linked branch, so the issue shows development activity immediately. Older gh versions fall back to a manual git checkout -b branch.

Does this workflow run end-to-end tests before opening the PR?▼

Yes. It runs bun run validate, bun run test, and targeted Playwright specs for the touched area. New user-visible behavior requires added or extended e2e coverage, and the full e2e suite runs only for cross-cutting changes.

Can I use this for Linear issues or PR reviews?▼

No. It is scoped to GitHub issues only; Linear issues use a separate linear-to-pr flow. It also does not create or triage issues, nor review or merge existing pull requests.

Why must Fixes #123 be in the PR body instead of commit messages?▼

GitHub's closing keywords only auto-close the issue when they appear in the PR body or title, not solely in commit messages, especially after a squash merge. Including it also surfaces the PR on the issue immediately.

Related Skills

Explore More Software Engineering Skills→
wuv-dreamguidewuv-dreamguide

openclaw-pr-maintainer

Automate OpenClaw PR review, triage, labeling, and merge preparation on GitHub.

Official
Advanced
Cohey0727Cohey0727

dev-pr-review

Reviews open GitHub pull requests in a worktree and merges, fixes, labels, or closes them.

Community
Advanced
WhaleylawWhaleylaw

ci-cd-testing-specialist

Automate GitHub Actions CI/CD test execution and PR reporting for Node web apps.

Community
Advanced
sorafujitanisorafujitani
1

pr:gen-linear

Generate formatted pull-request descriptions linked to Linear issues from committed changes.

Community
Intermediate