open-pr

Create a branch, commit with Conventional Commits, and open a pull request to staging.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/Thawatchai-Petkaew/campvibe --skill open-pr-thawatchai-petkaew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/Thawatchai-Petkaew/campvibe/tree/main/.claude/skills/open-pr
Command: npx skills add https://github.com/Thawatchai-Petkaew/campvibe --skill open-pr-thawatchai-petkaew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of creating a pull request (PR) for individual, atomic stories in a project, ensuring better code organization and reviewability.

Core Features & Use Cases

  • Branch Creation: Automatically creates a new branch based on a specific template.
  • Conventional Commits: Guides the use of Conventional Commits for atomic changes.
  • PR Opening: Automates the creation of a PR from the newly created branch.
  • Use Case: Ideal for software development workflows where each PR should correspond to a single, actionable task.

Quick Start

Execute the open-pr skill to initiate the process of opening a PR for your atomic story.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I automate creating a GitHub pull request for an atomic story?

You can automate opening a pull request by executing a script that creates a new branch, commits changes using Conventional Commits, and utilizes gh CLI commands to open a PR targeting the staging branch.

What is the best way to manage Git branches for individual story tasks?

Managing Git branches for individual story tasks is best handled by creating a new branch based on a specific template for each atomic story, ensuring better code organization and reviewability before opening a pull request.

Do I need the gh CLI installed to automate pull request creation?

Yes, you need the gh CLI installed and properly authenticated with GitHub, because the automation utilizes gh CLI commands to open the pull request for your atomic story.

How does Conventional Commits improve the pull request workflow?

Conventional Commits improves the pull request workflow by guiding atomic changes for individual stories, which ensures better code organization and enhances the reviewability of the PR targeting the staging branch.

Can I target a branch other than staging when opening a pull request?

Targeting a branch other than staging is not supported by this specific automation, which is designed to open a pull request specifically targeting the staging branch for an atomic story.