create-pr

Create pull requests from conventional commits using GitHub CLI.

17|3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/jidohyun/NOD --skill create-pr-jidohyun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/jidohyun/NOD/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/jidohyun/NOD --skill create-pr-jidohyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of high-quality pull requests with consistent titles and descriptions by parsing conventional commits and using the GitHub CLI.

Core Features & Use Cases

  • Parse conventional commits to generate PR titles and bodies.
  • Automatically create PRs via gh pr create.
  • Ensure linked issues and clear verification steps in PR descriptions.

Quick Start

Use the GitHub CLI to create a PR from the current branch so the title and description derive from conventional commits.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation from conventional commits?

Automating pull request creation from conventional commits requires parsing the git history to generate consistent PR titles and bodies, then executing GitHub CLI commands to publish the branch changes.

Does automated PR generation work with GitHub CLI and CI pipelines?

Automated PR generation works with GitHub CLI and CI pipelines by analyzing conventional commit messages from the current branch and executing gh pr create to publish the metadata-rich pull request.

What is the best way to ensure consistent PR titles and bodies in a dev workflow?

Ensuring consistent PR titles and bodies in a dev workflow is best achieved by parsing conventional commits to automatically derive structured metadata, including linked issues and clear verification steps, for the pull request.

How to generate PR descriptions with linked issues and verification steps?

Generating PR descriptions with linked issues and verification steps involves parsing conventional commit history to extract the relevant context, which is then formatted into the pull request body via GitHub CLI.

Do I need GitHub CLI installed to automate pull request creation?

You need the GitHub CLI installed and authenticated to automate pull request creation, because the process relies on the gh pr create command to parse conventional commits and publish the pull request.