Pr description

Skill contextosai/skills/skills/pr-description

A collection of Agent Skills — self-contained folders that teach AI agents to perform specialized tasks. Includes a production-readiness harness-audit skill, a plugin marketplace, a SKILL.md spec, and CI validation.

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.

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

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.

SKILL.md

1.2 KB, 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.