pr

Create pull requests for committed changes using project branch strategy.

Updated Jun 5, 2024
One-click install
npx skills add https://github.com/trysmr/dotfiles --skill pr-trysmr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/trysmr/dotfiles/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/trysmr/dotfiles --skill pr-trysmr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a pull request for the committed changes following the project's branch strategy.

Core Features & Use Cases

  • Base branch resolution: Detects whether to use main or staging as the PR base.
  • Change verification: Shows git status, recent commits, and diffs to ensure correct changes.
  • Quality checks: Executes project-specific tests/lint commands when possible before PR creation.
  • PR preparation: Generates a clean PR title and body template to describe changes.

Quick Start

現在の HEAD からプルリクエストを作成します。ブランチ戦略に従い、staging が存在すればそれをベースに、なければ main をベースとします。

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pull request creation from my committed changes?

Automate pull request creation by running this Skill, which detects your project's branch strategy, validates changes against tests and linters, generates a PR title and description, and creates the PR to the appropriate base branch—main or staging—using the GitHub CLI.

How does the Skill determine which branch to use as the PR base?

The Skill reads your project's README for branch strategy documentation, inspects available git branches, and automatically selects staging as the base if it exists; otherwise it uses main.

What checks does the Skill run before creating a pull request?

Before PR creation, the Skill shows git status and recent commits, runs project-specific test and lint commands to verify code quality, and prompts you for approval before invoking gh pr create.

Can I use this Skill with my project's existing branch naming conventions?

Yes. The Skill works with standard workflows including hotfix/*, staging, and main branches. It reads your README to understand your specific branch strategy and adapts accordingly.

What do I need set up before using this Skill to create pull requests?

You need committed changes on a feature branch, the GitHub CLI (gh) installed and authenticated, test and lint command configurations in your project, and a README documenting your branching strategy.