skills.rest
kartuli-app
kartuli-appOFFICIAL
Explore all skills by this author →
GitHub

pr-title-and-description

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

Updated Sep 26, 2025
Search Tags:#github#diff#pr#generate#pull-request#conventional-commit#pr-description
One-click install
npx skills add https://github.com/kartuli-app/kartuli --skill pr-title-and-description
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-title-and-description
Source: https://github.com/kartuli-app/kartuli/tree/main/.agents/skills/pr-title-and-description
Command: npx skills add https://github.com/kartuli-app/kartuli --skill pr-title-and-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull requests often lack concise, conventional-commit style titles and a complete, template-compliant description summarizing all substantive changes, which makes reviews slower and release notes less reliable. This Skill helps transform branch diffs and commit context into a ready-to-paste PR title and a full markdown description that follows the repository's PR template.

Core Features & Use Cases

  • Conventional commit title: Produce a single-line, conventional-commit formatted PR title (type(scope): short description).
  • Template-complete description: Generate a markdown PR body that fills the repository's pull request template sections (Description, Linked Issues, Type, Scope, Testing notes, etc.) by analyzing diffs and commit messages.
  • Context-aware summarization: Inspect config and source file diffs to identify multiple themes (e.g., tooling, refactors, feature work) and include linked issue references when provided.
  • Use Case: When preparing a feature branch for review, use this Skill to create a clear title and a thorough description that documents scope, testing steps, and any preview notes.

Quick Start

Draft a PR title and full description for the current branch compared to origin/main, and include "Closes #N" if you provide an issue number.

Frequently Asked Questions about pr-title-and-description

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

FAQPage Schema
How do I generate a pull request description from a branch diff?▼

To generate a pull request description, this Skill inspects your branch diff against main and commit context to produce a full markdown description summarizing code and configuration changes. It automatically fills repository template sections for ready-to-paste PR bodies.

Can I automatically create conventional commit PR titles from git diffs?▼

Yes, you can create conventional commit PR titles from git diffs by analyzing the branch changes against main. The Skill generates a single-line title formatted as type(scope): short description based on the substantive code and documentation modifications.

How do I fill out a GitHub pull request template automatically?▼

To fill out a GitHub pull request template automatically, the Skill references .github/pull_request_template.md when available and uses diff context to populate Description, Type, Scope, and Testing notes sections with relevant code change summaries.

What's the best way to summarize multiple code changes for a PR review?▼

The best way to summarize multiple code changes for a PR review is context-aware diff analysis that identifies distinct themes like refactors and feature work. The Skill groups related file modifications into a structured markdown description for faster reviews.

Does this PR generator include linked issue references in the description?▼

Yes, the PR generator includes linked issue references in the description. When you provide an issue number, it appends references like Closes #N to the markdown body alongside the summarized branch diff context.

What pull request template format does this PR description generator support?▼

This PR description generator supports standard markdown pull request templates stored at .github/pull_request_template.md. It parses existing template sections and injects summarized diff content to produce a template-compliant markdown PR body.

Related Skills

Explore More Software Engineering Skills→
rjernstrjernst
1

pr

Create a GitHub pull request from the current branch with commit history and diff context.

Community
Intermediate
ryan-mahoneyryan-mahoney

pr

Open a GitHub pull request linked to an issue from a branch name.

Community
Intermediate
angelriera-devangelriera-dev

git-commit

Analyze staged diffs to generate conventional commit messages with safety checks.

Community
Advanced
shopwareLabsshopwareLabs
41

pr-description-writing

Draft conventional commit PR titles and Shopware 5-section descriptions.

Official
Advanced