skills.rest
fbosch
fboschCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ai-pr

Generate structured PR descriptions from git diffs and commit history.

3|Updated Jun 23, 2022
Search Tags:#automation#generate#code-review#pull-request#pr-description#git-diff
One-click install
npx skills add https://github.com/fbosch/dotfiles --skill ai-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-pr
Source: https://github.com/fbosch/dotfiles/tree/main/.agents/skills/ai-pr
Command: npx skills add https://github.com/fbosch/dotfiles --skill ai-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate concise PR descriptions from git diffs and commit context. Use when the user asks to create a PR description, write a pull request summary, or needs help documenting changes for code review. Automatically analyzes git diffs and commit history to produce well-structured PR descriptions with summary, changes, testing info, and breaking changes.

Core Features & Use Cases

  • Auto-analyzes git diffs and commit history to produce structured PR descriptions.
  • Enforces hard limits for Summary, Changes, Testing, and Breaking Changes.
  • Works across small to large changes and supports code-review workflows.

Quick Start

Provide a concise PR description for the latest diff in the current branch.

Frequently Asked Questions about ai-pr

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

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

You can generate a PR description by feeding a git diff and commit history into an automation tool, which analyzes the changes and outputs a structured summary with bullet points, testing notes, and breaking changes.

What is the best way to write pull request summaries for large code changes?▼

Writing pull request summaries for large changes is best handled by automating the extraction of key modifications from the git diff, ensuring the final output includes a concise summary, specific changes, and testing information.

Can I automate code review documentation using commit history and diffs?▼

Yes, you can automate code review documentation by processing commit history and diffs to produce deterministic descriptions, enforcing hard limits like a one-sentence summary and explicit testing and breaking change lines.

Does automated PR generation work for both small and large git diffs?▼

Automated PR generation works across small to large git diffs, applying consistent code review workflows to produce structured sections for summaries, changes, testing info, and breaking changes regardless of scope.

What sections should a well-structured pull request description contain?▼

A well-structured pull request description should contain a one-sentence summary, two to five bullet points of changes, testing notes, and an explicit line for breaking changes to support thorough code review.

Related Skills

Explore More Software Engineering Skills→
paulchiupaulchiu
3

write-pull-request

Generate pull request descriptions from git diff and commit history.

Community
Intermediate
lie5860lie5860
30

chinese-git-workflow

Generate Git workflows for Gitee, Coding.net, and JihuLab/GitLab.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic