Pr title description

Skill kin0992/dev-toolkit/packages/skills/src/git/pr-title-description

Platform Engineering toolkit: reusable GitHub Actions, AI Skills, and shared TypeScript configs.

Install

npx -y skills add kin0992/dev-toolkit --skill pr-title-description

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

**UTILITY SKILL** - Generate a pull request title and description from a branch diff. USE FOR: write PR description, generate pull request title, summarize branch for reviewers, create PR body from commits, draft pull request. DO NOT USE FOR: writing commit messages (use commit-message skill), code review feedback, changelog generation. INVOKES: git log and git diff for reading branch changes, file reading for PR templates. FOR SINGLE OPERATIONS: Use git log --oneline directly for a quick branch summary.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, as published. Nobody here has run it

Generate a PR title and description

Summarize a branch for reviewers with a concise PR title and markdown description.

Instructions

Read commits, diff, and optional template before writing.
Write a title: imperative mood, ≤72 chars, summarizing the primary user-facing change.
If a PR template is provided, fill its sections. Otherwise use:
- Why – motivation or linked context
- What – concise bullets grouped by area
- How to verify – checks or tests for reviewers
- Risks / follow-ups – anything to watch closely Omit empty sections.
Describe intent and outcome, not every edit. Never fabricate ticket numbers, links, or steps.

Output

Return only the title and description:

TITLE: <pr title>

<description in markdown>

Example

TITLE: Add retry handling for webhook delivery

## Why
Transient outages could permanently fail webhook delivery.

## What
- retry failed deliveries before marking them failed
- emit retry metrics
- document retry behavior

## How to verify
- review retry path tests
- confirm metrics for retries and terminal failures

Common edge cases

If a template includes required headings, preserve them.
If verification details are missing, do not invent steps.