skills.rest
northguild
northguildOFFICIAL
Explore all skills by this author →
GitHub

pr-desc

Generates a PR title and description from the git diff against main.

6|Updated Mar 10, 2026
Search Tags:#code review#pull request#conventional commits#github#git diff#changesets#pr description
One-click install
npx skills add https://github.com/northguild/gmt --skill pr-desc-northguild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-desc
Source: https://github.com/northguild/gmt/tree/main/.agents/skills/pr-desc
Command: npx skills add https://github.com/northguild/gmt --skill pr-desc-northguild

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a clear, consistent pull request title and description is repetitive work, and reviewers often receive vague or incomplete PRs. This Skill inspects the commits and diff on your current branch versus main and produces a structured, copy-paste-ready PR title and description. ## Core Features & Use Cases - Diff-driven generation: Runs git log and git diff against main to ground every claim in the actual changes, never fabricating file names. - Structured output format: Produces a Conventional Commits title plus Summary, What Changed, Why, Validation, Risk/Impact, Release, and Checklist sections. - Changeset awareness: Reports the changesets in .changeset/ and their bump level so reviewers understand release impact. - Use Case: After finishing a feature branch, ask for a PR description and receive a complete markdown block ready to paste into GitHub, with the title under 72 characters and grouped change sections. ## Quick Start Ask the assistant to write a PR description for the current branch compared to main.

Frequently Asked Questions about pr-desc

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

FAQPage Schema
How do I generate a PR description from my git diff?▼

Run this Skill on your feature branch and it executes git log main..HEAD and git diff main...HEAD to inspect commits and changed files. It then groups related changes and outputs a complete markdown PR description ready to paste into GitHub.

What format does the generated PR title follow?▼

The title follows Conventional Commits with a type, scope, and description, such as feat(domination): calendar boundaries (CORE-5, #186). It is kept under 72 characters and matched against recent commit message style via git log.

Does this Skill create the pull request on GitHub?▼

No, it never creates the PR itself. It only outputs the title and description in a plain fenced code block for you to copy, and the repository owner opens every PR manually.

Can the PR description include changeset release information?▼

Yes, the Release section lists the changesets found in the .changeset/ directory along with their bump level. If merging publishes nothing, the description states that explicitly for reviewers.

What happens if a PR section has no content?▼

Sections with nothing to report are omitted entirely rather than filled with placeholder text like N/A. This keeps the final description concise and focused on actual changes.

Related Skills

Explore More Software Engineering Skills→
mykaarmamykaarma

git-commit

Create conventional commit messages and push code changes.

Official
Intermediate
bihaviourbihaviour

gh

Automate GitHub pull request creation, merging, and draft issue generation.

Official
Advanced
DataDogDataDog
648

lint

Run Hatch-based lint, format, and quality checks on modified files.

Official
Advanced
Luney-IndustriesLuney-Industries
4

code-review

Automate GitHub pull request code reviews with inline comments and summaries.

Official
Advanced