github-pr

Creates GitHub pull requests after running tests, lint, and CI checks.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/dwayneparton/claude --skill github-pr-dwayneparton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/dwayneparton/claude/tree/main/skills/github-pr
Command: npx skills add https://github.com/dwayneparton/claude --skill github-pr-dwayneparton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually preparing a pull request involves many error-prone steps: verifying the branch, running tests and linters, checking CI workflows, pushing, and writing a proper PR description. This Skill automates that entire pre-PR checklist so nothing gets skipped. ## Core Features & Use Cases - Branch Verification: Confirms you are on a feature branch and creates one from main/master if needed, preventing accidental pushes to protected branches. - Pre-PR Quality Gates: Runs available test, lint, and format commands and inspects .github/workflows to catch CI failures locally before opening the PR. - Structured PR Creation: Pushes the branch and opens the PR via the gh CLI with a consistent Summary and Test plan body template. - Use Case: After finishing a bug fix on a feature branch, invoke the Skill to run the test suite, push the branch, and open a properly formatted PR, returning the PR URL for review. ## Quick Start Send up my current changes as a GitHub pull request.

Frequently Asked Questions about github-pr

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

FAQPage Schema
How do I create a GitHub pull request from the command line?

Use the gh CLI with gh pr create, passing a title and body. This Skill automates the full flow: it verifies your feature branch, runs tests and lint, pushes with git push -u origin, then opens the PR and returns its URL.

How to run tests and lint before opening a pull request?

Check the project for available commands in package.json scripts or a Makefile, then run test, lint, and format checks before pushing. This Skill runs them automatically and fixes failures rather than skipping or silencing them.

What happens if I am on main when creating a pull request?

The Skill never pushes directly to main or master. If you are on a default branch, it creates a descriptive feature branch with git checkout -b, stages and commits your changes, then proceeds with the PR.

Does this Skill merge or force-push pull requests?

No. It never merges PRs and never force-pushes or amends commits without explicit user approval. PRs are opened for human review and merge, keeping the workflow safe by default.

Why check .github/workflows before opening a PR?

Reading workflow files reveals which CI checks will run on the PR, such as type-check, lint, or test jobs. Running those same checks locally first catches failures early and avoids red CI on the opened PR.