create-pr

Create GitHub pull requests targeting the dev branch with gh pr create.

132|9|Updated Mar 16, 2022
One-click install
npx skills add https://github.com/mikotoIO/mikoto --skill create-pr-mikotoio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/mikotoIO/mikoto/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/mikotoIO/mikoto --skill create-pr-mikotoio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies creating a pull request by automating the GitHub CLI workflow, reducing manual steps and errors.

Core Features & Use Cases

  • Automated PR creation: Pushes your changes and opens a PR with gh pr create, ensuring the base branch is dev.
  • Workflow consistency: Standardizes PR messaging and branch naming conventions across teams.
  • Use Case: When finishing a feature branch, quickly generate a PR to the dev branch for code review and integration.

Quick Start

Push the current branch to origin if needed, then run gh pr create to open a PR against the dev branch.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I create a pull request using the GitHub CLI?

Yes, you can automate pull request creation by running the gh pr create command. This requires having the gh CLI installed, proper repository access, and a pushed feature branch to generate the PR URL for review.

Do I need to install anything specific to automate GitHub PR creation?

When you finish developing a feature branch, you need to create a pull request to initiate code review and integration. Automating PR creation standardizes branch naming and messaging conventions across your development team.

What is the best way to ensure PR consistency across a development team?

Automating pull request creation targets the dev branch as the base for your feature branch. Standardizing this workflow ensures that all code reviews and integrations consistently merge features into the correct development branch.

Why does automated pull request creation require a pushed branch?

Automated pull request creation targets the dev branch as the base for your feature branch. Standardizing this workflow ensures that all code reviews and integrations consistently merge features into the correct development branch.