git-pr

Name: git-pr
Availability: InStock
Author: nvimcraft

Generate pull request metadata from Git change sets for GitHub, Gitea, and Forgejo.

Updated Feb 7, 2026

Search Tags:#git #code analysis #pull request #conventional commits #github #branch naming

Ready to run

npx skills add https://github.com/nvimcraft/dotfiles-macos --skill git-pr-nvimcraft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-pr
Source: https://github.com/nvimcraft/dotfiles-macos/tree/main/.config/opencode/skills/git-pr
Command: npx skills add https://github.com/nvimcraft/dotfiles-macos --skill git-pr-nvimcraft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of writing consistent pull request metadata by analyzing code changes and turning them into structured branch names, titles, and descriptions.

Core Features & Use Cases

PR Content Generation: Creates Angular-style PR titles, summaries, and descriptions from staged or current Git changes.
Change Analysis: Infers the appropriate commit type and branch naming convention from modified files and code patterns.
Use Case: Developers can use this Skill after completing a feature or fix to quickly prepare a review-ready PR draft while keeping Git operations manual and controlled.

Quick Start

Ask the git-pr skill to analyze my latest code changes and generate a pull request draft.

Frequently Asked Questions about git-pr

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

FAQPage Schema

How do I generate a pull request description from staged git changes?▼

You can generate a pull request description from staged git changes by analyzing modified files to infer change classification and formatting a structured PR summary with conventional commit titles. This skill produces review-ready PR drafts directly from code changes.

Does this skill perform git operations like committing or pushing branches automatically?▼

No, this skill does not perform git operations automatically. It strictly analyzes code change sets to generate PR metadata like branch names and titles, ensuring developers keep Git operations manual and controlled while drafting pull requests.

Can I use conventional commit formatting for GitHub, Gitea, and Forgejo pull requests?▼

Yes, you can apply conventional commit formatting for GitHub, Gitea, and Forgejo pull requests. The skill analyzes code patterns to infer appropriate commit types and generates Angular-style PR titles compatible with these platforms.

How does breaking change detection work when generating PR titles?▼

Breaking change detection works by analyzing modified files and code patterns within the change set to identify significant modifications. The skill then flags these breaking changes and reflects them in the generated conventional commit-style PR titles and descriptions.

What is the best way to create branch names from code modifications?▼

The best way to create branch names from code modifications is to analyze modified files and infer appropriate branch naming conventions automatically. The skill evaluates code patterns to generate structured branch names aligned with the detected change classification.

How do I classify software changes for feature, fix, or refactor pull requests?▼

You classify software changes for features, fixes, or refactors by analyzing modified files and code patterns to infer the appropriate commit type. The skill maps these classifications into conventional commit-style PR titles and structured descriptions.