Pr description

Skill vaibhavsaxena022/skills/pr-description

Generate a structured pull-request description from the diff between the current branch and its base. Use when opening a PR or when asked to write a PR description. Produces Summary, Changes, Testing, and Risks sections.From its SKILL.md

Install

npx -y skills add vaibhavsaxena022/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

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.

SKILL.md

1.4 KB, 236 tokens by cl100k_base, as published. Nobody here has run it

PR Description

Write a clear, reviewer-friendly pull-request description from the branch's changes.

Steps

Determine the base branch (usually main). Run:
- git log <base>..HEAD --oneline — the commits in scope
- git diff --stat <base>...HEAD — the files touched
Read the actual diff of the most significant files to understand intent, not just lines.

Produce these sections:

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

## Changes
- grouped by area/module, behavior-focused

## Testing
- tests added/updated, and manual verification steps

## Risks / Rollout
- DB migrations, new env vars, config, backward-compat, feature flags

Rules

Describe behavior and intent — not a file-by-file dump.
Explicitly call out DB migrations, breaking changes, and new environment variables.
Keep it skimmable. If the branch name references an issue, link it; don't invent one.

What ships with it

Read from the repository

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