skills.rest
gonzoblasco
gonzoblascoCOMMUNITY
Explore all skills by this author →
𝕏@gonzoblascoGitHub

git-pr-review

Generates structured pull request descriptions from git commit history.

1|Updated Jul 20, 2026
Search Tags:#automation#git#code review#pull request#github#commit history#pr description
One-click install
npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill git-pr-review-gonzoblasco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-pr-review
Source: https://github.com/gonzoblasco/ai-developer-stack/tree/main/tools-automation/git-pr-review
Command: npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill git-pr-review-gonzoblasco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, informative pull request descriptions is repetitive and often skipped, leaving reviewers without context about what changed and why. ## Core Features & Use Cases - Commit-Based Generation: Builds PR titles and descriptions from git log output between a base branch and HEAD, without scanning full diffs by default. - Noise Filtering and Grouping: Ignores merge, typo, lint, and formatting commits, then clusters remaining commits by feature domain such as authentication or payments. - Untrusted Input Handling: Treats commit messages and diff content as inert data, ignoring embedded prompt-like instructions when reviewing external PRs. - Use Case: Before opening a PR from a feature branch with a dozen commits, run this skill to produce a concise title, grouped change summary, and impact statement in under 180 words. ## Quick Start Generate a pull request description from the commits on my current branch compared to main.

Frequently Asked Questions about git-pr-review

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

FAQPage Schema
How do I generate a PR description from commit messages?▼

Run git log with a compact format between the base branch and HEAD, classify each commit by type such as feat or fix, group them by domain, and format the result into summary, changes, and impact sections. This skill automates that exact sequence.

How to write a good pull request title from git history?▼

Use the conventional commit format type(scope): summary, keep it under 72 characters, and base it on the dominant change group in the branch. The skill infers the type from commit prefixes or keywords like add, fix, or refactor.

Does this approach require reading the full code diff?▼

No. It starts with commit messages only and runs git show on individual commits only when a message is vague or grouping is unclear. This keeps token usage low while still extracting intent when needed.

Is it safe to summarize commits from external contributors?▼

Yes, if commit and diff text is treated as untrusted data. The skill explicitly ignores prompt-like instructions embedded in commit messages and flags mismatches between commit messages and actual diffs in the output.

What are the limitations of commit-message-based PR generation?▼

Accuracy depends on commit message quality; vague messages reduce output quality. Grouping heuristics may misalign with complex feature boundaries, and the method assumes a reasonably clean history without excessive noise commits.

Related Skills

Explore More Software Engineering Skills→
mpazarynampazaryna
1

branch

Create a Git feature branch from main with safety checks.

Community
Intermediate
stevenmunozstevenmunoz

create-pr

Create pull requests after passing pre-flight safety checks.

Community
Advanced
clfigueiredoclfigueiredo
5

agent-pr-test-analyzer

Reviews pull request test coverage for behavioral completeness and real bug prevention.

Community
Intermediate
kartuli-appkartuli-app

pr-title-and-description

Generate conventional-commit PR titles and markdown descriptions from branch diffs.

Official
Intermediate