Pr describe

Skill senior-sigan/llm-skills/skills/pr-describe

Install

npx -y skills add senior-sigan/llm-skills --skill pr-describe

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 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

Generate PR title (conventional commits) and description by analyzing branch changes. Use when creating or describing a pull/merge request.

SKILL.md

2.6 KB, 593 tokens by cl100k_base, as published. Nobody here has run it

/pr-describe — Generate Pull Request Description

Generate a PR title and description based on the current branch changes.

Algorithm

1. Gather context

# Current branch
git branch --show-current

# Commit log from branch point
git log --oneline main..HEAD

# Scope of changes — understand what's affected first
git diff main...HEAD --stat

# Full diff — change details
git diff main...HEAD

2. Generate PR title

The title becomes the squash commit message, so strictly follow Conventional Commits:

<type>(<scope>): <short description>

Types:

feat — new functionality
fix — bug fix
refactor — code change without behavior change
docs — documentation
test — tests
chore — maintenance, dependencies, CI
perf — performance improvement

Rules:

Imperative mood: "add", not "added" or "adds"
72 characters max
No period at the end
scope — module or area affected by the changes (optional)
Breaking change: feat(api)!: restructure response format

3. Generate PR description

Use this template:

## Task
<!-- Link to issue (if found in commits or branch name) and description in own words -->
<Task description: what needed to be done and why>

## Changes
<!-- Key changes — solution logic, not a diff retelling -->
- <Change 1>
- <Change 2>
- ...

## Why this approach
<!-- Explain the chosen approach if non-obvious. Remove this section for trivial changes -->

## How to verify
<!-- Concrete steps for the reviewer -->
1. <Step 1>
2. <Step 2>
3. Expected result: ...

4. Output result

Output in this format:

### PR Title
<title>

### PR Description
<description using the template>

Rules

Analyze ALL branch commits, not just the latest — the PR describes the entire body of work
Title should reflect the outcome for the user/system, not the process ("add user search" not "implement search functionality")
"Changes" section — list logical changes (what the system can do now), not files
"How to verify" — be specific: endpoint, command, UI button. The reviewer should be able to verify in 2 minutes
"Why this approach" — include only when the choice is non-obvious or alternatives were considered. Remove for trivial changes
If the branch name or commits contain an issue number (PROJ-123, #456) — include it in the "Task" section

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 3 of the 12 instructions most pr commit review skills give in 593 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07

Use conventional commits formathere, and in 127 of 888, across 115 files
Keep subject line under 72 charactershere, and in 62 of 888, across 48 files
Delete branches after mergein 51 of 888, across 38 files
Use imperative mood in subject linehere, and in 51 of 888, across 42 files
Use imperative mood in commit messagesin 44 of 888
Verify directory is ignored before creating worktreein 43 of 888, across 12 files
Generate a conventional commit messagein 43 of 888
Add unignored worktree directories to gitignorein 42 of 888, across 10 files
Make atomic commitsin 39 of 888, across 27 files
Run tests before committingin 36 of 888, across 25 files
Verify clean test baselinein 35 of 888, across 9 files
Split unrelated changes into separate commitsin 35 of 888, across 30 files

Said here and by no other author read

describe logical changes not files
list specific verification steps
include issue links in the task section

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.