skills.rest
GeneralJerel
GeneralJerelCOMMUNITY
Explore all skills by this author →
GitHub

create-pr-description

Generate structured PR descriptions from staged git changes and PR conventions.

6|Updated Feb 19, 2026
Search Tags:#automation#git#diff#pr#description#code-review#pull-request
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-pr-description-generaljerel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr-description
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/create-pr-description
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-pr-description-generaljerel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually drafting PR descriptions is time-consuming and error-prone; this Skill analyzes the current staged git changes to generate a structured, reviewer-friendly PR body.

Core Features & Use Cases

  • Analyzes staged diffs to summarize changes and rationale
  • Aligns with repository PR conventions when present and applies a consistent template
  • Produces a ready-to-paste PR body including sections like Why changed, Files touched, and Testing notes

Quick Start

Generate a PR description from the staged changes.

Frequently Asked Questions about create-pr-description

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 automatically?▼

To generate a pull request description from staged git changes, you can use a tool that analyzes the git diff --cached output to automatically summarize why changes were made, what files were touched, and how to test them.

What is the best way to write a structured PR body from a git diff?▼

Writing a structured PR body from a git diff is best handled by analyzing the staged changes and formatting the rationale, modified files, and testing notes into a ready-to-paste template that aligns with repository conventions.

Can I align automated PR descriptions with my existing repository conventions?▼

You can align automated PR descriptions with existing repository conventions by using a generation tool that reads your project's specific PR templates and applies them to the analyzed git diff output for consistent formatting.

How do I ensure my pull request includes testing notes from my code changes?▼

To ensure a pull request includes testing notes from code changes, generate the PR body by analyzing the staged git diff, which structures the output to explicitly include sections for why the change was made and how to test it.

What should a reviewer-friendly pull request description contain when drafting from a git diff?▼

A reviewer-friendly pull request description drafted from a git diff should contain a structured summary of the staged changes, including the rationale for modifications, the files touched, and specific testing notes for validation.

Why do manually drafted PR descriptions fail to capture the full git diff context?▼

Manually drafted PR descriptions fail to capture full git diff context because human summaries often miss file-level details, whereas automated analysis of staged changes ensures all modified files and rationales are included.

Related Skills

Explore More Software Engineering Skills→
williabywilliaby
2

pr-prepare

Generate Markdown pull request descriptions from git status, log, and diffs.

Community
Basic
flora131flora131
484

gh-create-pr

Commits unstaged changes, pushes the current branch to remote, and initiates a pull request.

Community
Basic
RafayelGardishyanRafayelGardishyan

check

Run golangci-lint, Biome, and svelte-check quality checks before commits.

Community
Intermediate
ruimfernandesruimfernandes

little

Generate commit messages and PR descriptions from repository diffs.

Community
Intermediate