Pr description

Skill contextosai/skills/skills/pr-description

Draft a pull request title and description from the commits and diff on the current branch. Use when the user asks to open a PR, write a PR description, or summarize a branch's changes for review.From its SKILL.md

Install

npx -y skills add contextosai/skills --skill pr-description

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

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.
runs commandsInstructs the agent to run 2 commands, including `git log --oneline <base>..HEAD` and 1 more.

SKILL.md

1.2 KB, 244 tokens by cl100k_base, as published. Nobody here has run it

PR Description

Produce a reviewer-friendly pull request title and body for the current branch.

Steps

Determine the base branch (usually main). Run git log --oneline <base>..HEAD and git diff <base>...HEAD to gather the full set of changes.
Group the changes by theme rather than listing every commit verbatim.
Fill in the template below.

Template

## Summary
<1–3 sentences: what this PR does and why.>

## Changes
- <key change 1>
- <key change 2>

## Testing
<How it was verified — commands run, manual checks, or "not yet tested".>

## Notes for reviewers
<Anything risky, intentionally out of scope, or needing a decision. Omit if none.>

Guidelines

Lead with intent: a reviewer should understand the why in the first sentence.
Be honest in the Testing section — if something wasn't tested, say so.
Keep the bullet list to the changes that matter for review, not noise.
Call out breaking changes and migrations explicitly.

What ships with it

Read from the repository

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

Gives 0 of the 12 instructions most pr commit review skills give in 244 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Lead with intent in the summary
Be honest in the testing section
Filter out noise from changes

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.