github-pr

Generate GitHub pull requests with conventional commits and structured descriptions.

Updated Nov 20, 2025
One-click install
npx skills add https://github.com/JFEspanolito/Template_FrontEnd_NextJS_JF --skill github-pr-jfespanolito
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/JFEspanolito/Template_FrontEnd_NextJS_JF/tree/main/AI/skills/curated/github-pr
Command: npx skills add https://github.com/JFEspanolito/Template_FrontEnd_NextJS_JF --skill github-pr-jfespanolito

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating high-quality Pull Requests, ensuring adherence to conventional commit standards and clear, informative descriptions.

Core Features & Use Cases

  • Conventional Commits: Enforces a structured commit message format for better changelog generation and automated tooling.
  • Structured PR Descriptions: Guides users to create PR descriptions that clearly outline the summary, changes, and testing status.
  • Use Case: When you've finished a feature, use this Skill to generate a PR title like feat(auth): implement two-factor authentication and a detailed description that includes a summary, list of changes, and testing status, closing the relevant issue.

Quick Start

Use the github-pr skill to create a pull request with the title "feat(api): add user endpoint" and a body describing the changes.

Frequently Asked Questions about github-pr

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

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

To create a GitHub pull request with conventional commits, use this Skill to generate structured PR titles like `feat(auth): ...` or `fix(api): ...` via the GitHub CLI. It enforces commit message types and formats the PR body automatically.

What should a structured pull request description include for effective code review?

A structured pull request description should include a clear summary, a detailed list of changes, and the current testing status. This Skill guides you to format these sections to facilitate effective code review.

Can I assign reviewers and labels when creating a draft PR from the command line?

Yes, you can assign reviewers and add labels when creating a draft PR from the command line. This Skill supports various PR creation scenarios, allowing you to include reviewers, labels, and draft status directly.

Why use conventional commit format for pull request titles?

Using conventional commit format for pull request titles ensures better changelog generation and enables automated tooling. This Skill enforces structured types like `feat`, `fix`, or `docs` to standardize your project history.

Does this GitHub PR generator support atomic commits?

Yes, this GitHub PR generator supports atomic commits. It provides examples for various PR creation scenarios, ensuring your changes are isolated and properly structured before submission.