Pr description

Skill K95M65/AI_ONBOARD/skills/pr-description

Write a clear pull-request description from the branch's commits and diff. Use when opening a PR or when asked to summarize a branch's changes for review.From its SKILL.md

Install

npx -y skills add K95M65/AI_ONBOARD --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.2 KB, 239 tokens by cl100k_base, as published. Nobody here has run it

PR description

When to use

Opening a PR, or summarizing a branch's changes for reviewers.

Steps

Gather the raw material: bash scripts/collect.sh [base] (base defaults to origin/main, falling back to main). It prints the commit subjects and the changed-file stat for base..HEAD.
Write the description from that material using the template below — explain the why, not just the what; the diff already shows the what.
Keep it honest: call out risk, follow-ups, and anything not covered by tests.

Template

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

## Changes
- <the notable changes, grouped; not a commit dump>

## Testing
- <what you ran / added, and the result>

## Risk & follow-ups
- <blast radius, migrations, anything deferred>

Notes

Lead with the problem being solved, not the implementation.
If the branch does several unrelated things, that's a signal to split the PR, not to write a longer summary.

What ships with it: 1 file

899 B alongside SKILL.md, 1 of them executable

scripts/

collect.shruns899 B