open-pr

Automates committing, pushing, and creating GitHub pull requests with Nx version plans.

23|5|Updated Apr 3, 2025
One-click install
npx skills add https://github.com/LedgerHQ/lumen --skill open-pr-ledgerhq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/LedgerHQ/lumen/tree/main/.claude/skills/open-pr
Command: npx skills add https://github.com/LedgerHQ/lumen --skill open-pr-ledgerhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening a pull request involves repetitive manual steps: creating a branch, writing conventional commits, ensuring an Nx version plan exists, pushing, and drafting a PR description. This Skill runs that entire flow automatically in one go. ## Core Features & Use Cases - End-to-end PR automation: Creates a feature branch from main if needed, commits uncommitted changes with a conventional commit message, pushes, and opens the PR via the GitHub CLI. - Nx version plan enforcement: Detects missing .nx/version-plans/ entries and creates one per affected package with patch frontmatter before opening the PR. - Structured PR body: Generates a PR description with Description (why), How to test (concrete steps), and Screenshots sections derived from the diff against main. - Use Case: You finished a bug fix on the Ledger Lumen design system and want a PR opened. Invoke the Skill and it commits your changes, adds the version plan, pushes, and returns a clickable PR link without asking for confirmation. ## Quick Start Ask the assistant to open a PR from the current branch to main using the open-pr skill.

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 with gh pr create --title "<title>" --base main --body-file <file>. This Skill automates that plus committing, pushing, and checking for an existing PR with gh pr view before creating a new one.

How to create an Nx version plan before opening a PR?▼

Check git diff main...HEAD --name-only -- .nx/version-plans/ to see if a plan exists. If not, create one .nx/version-plans/version-plan-<timestamp>-<pkg>.md file per affected package with single-package patch frontmatter.

Does this work if I am on the main branch?▼

Yes, but it first asks for a Jira ticket number, generates a descriptive branch name from uncommitted changes, and creates a branch named DLS-<number>-<branch-name> before continuing the PR flow.

What happens if a pull request already exists for my branch?▼

The Skill runs gh pr view --json url to detect an existing PR. If one exists, it prints the existing PR URL and stops instead of creating a duplicate.

Why does gh pr create fail with an authentication error?▼

The GitHub CLI must be installed and authenticated. Install it from cli.github.com and run gh auth login, then rerun the command to create the PR successfully.