git-pr-create

Create pull requests with titles and descriptions from git logs.

Updated Dec 2, 2025
One-click install
npx skills add https://github.com/qlawmarq/dotfiles-common --skill git-pr-create-qlawmarq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pr-create
Source: https://github.com/qlawmarq/dotfiles-common/tree/main/skills/git-pr-create
Command: npx skills add https://github.com/qlawmarq/dotfiles-common --skill git-pr-create-qlawmarq

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill streamlines the process of creating pull requests by ensuring they have clear titles, comprehensive descriptions, and adhere to best practices, reducing the manual effort and potential for oversight.

Core Features & Use Cases

  • Automated PR Generation: Creates pull requests with titles and descriptions derived from commit logs.
  • Best Practice Adherence: Analyzes changes to generate informative descriptions and checks for PR templates.
  • Use Case: After completing a feature and committing your changes, use this skill to automatically generate a pull request ready for review, complete with a summary of your work.

Quick Start

Use the git-pr-create skill to create a pull request for the current branch.

Frequently Asked Questions about git-pr-create

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

FAQPage Schema
How do I automate pull request creation from git commit logs?

Automating pull request creation involves analyzing git logs and diffs to generate titles and descriptions, ensuring changes are summarized automatically for efficient code review workflows.

How do I generate a pull request description that follows project templates?

Generating a pull request description that follows project templates requires analyzing git diffs and checking for existing PR templates to ensure adherence to best practices and comprehensive summaries.

Do I need the GitHub CLI to create pull requests automatically?

Yes, you need the GitHub CLI (`gh`) installed to automate pull request creation, as it handles the underlying push operations and PR creation against the GitHub repository.

What is the best way to create well-structured pull requests for code review?

The best way to create well-structured pull requests is by deriving titles and descriptions directly from commit logs and diffs, reducing manual effort and ensuring informative context for reviewers.

Can I use this automation for any git branch before pushing code?

You can use this automation for your current working branch, but the process requires pushing your committed changes to the remote repository before the GitHub CLI can execute the PR creation.