open-pr

Stage, commit, push, and open a GitHub pull request following repository conventions.

3|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ronaknnathani/relay --skill open-pr-ronaknnathani
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/ronaknnathani/relay/tree/main/skills/open-pr
Command: npx skills add https://github.com/ronaknnathani/relay --skill open-pr-ronaknnathani

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Finished work often sits uncommitted or gets pushed with sloppy commit messages, wrong branches, and PR descriptions that ignore the repository's house style. This Skill takes completed changes from the working tree to an open pull request while enforcing the repo's commit conventions, PR template, and AGENTS.md rules. ## Core Features & Use Cases - Safe branching and staging: Refuses to commit on the default branch, creates a prefixed branch via the relay config, and stages only the specific files for the change. - Convention-aware commits and PRs: Matches the repository's commit message style, keeps refactors separate from features, fills the repo's PR template when present, and writes a prose summary with a Testing Done command list. - Optional pre-push review and draft PRs: Runs a local diff review before pushing (skippable with --no-review) and supports opening draft PRs with --draft. - Use Case: After implementing a bug fix across three files, invoke the Skill to branch off main, commit with a repo-style message including the agent's Co-authored-by trailer, push, and open a PR whose body follows the repo template. ## Quick Start Ask the agent to commit the finished changes and open a pull request for them, optionally as a draft.

Frequently Asked Questions about open-pr

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

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

Use the GitHub CLI command gh pr create with a title and body file after pushing your branch. This Skill wraps that flow in a helper script that stages files, commits, pushes, and calls gh pr create with optional --draft support.

How to commit changes without committing on the main branch?▼

Detect the default branch first, then create a new branch before committing. The Skill's ensure-branch command checks the current branch against the detected default and creates a prefixed branch using the relay config branch-prefix setting.

Does gh pr create support draft pull requests?▼

Yes, gh pr create accepts a --draft flag to open the PR as a draft instead of ready for review. Pass --draft to this Skill and it forwards the flag to the create-pr helper command.

Can I use a repository PR template when opening a pull request?▼

Yes, the helper fetches the repository's pull request template via gh repo view and fills each section from the actual change. A fallback prose body with a Testing Done section is used only when no template exists.

Why should I avoid git add . before committing?▼

Staging the whole tree mixes unrelated changes, formatting churn, and potential secrets into one commit. Stage only the specific files belonging to the change so the diff stays clean and reviewable.