Pr description

Skill LichAmnesia/awesome-antigravity-skills/skills/pr-description

A curated list of awesome Agent Skills, skill collections, and resources for Google Antigravity — the agent-first IDE powered by Gemini 3

Install

npx -y skills add LichAmnesia/awesome-antigravity-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

20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
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

Generates a reviewer-friendly pull request description from the branch diff. Use when opening a PR, when asked to summarize a branch, or before requesting review.

SKILL.md

1.8 KB, as published. Nobody here has run it

PR Description

Produce a PR description a busy reviewer can act on in under a minute.

When to use this skill

The user asks to open a PR or "write the PR description".
A branch is ready and needs a summary before review.

How to use it

Collect the real change surface — never write from memory:
```
git log main..HEAD --oneline
git diff main...HEAD --stat
```
Structure the description:
- What — 1-2 sentences: the user-visible outcome, not the mechanics.
- Why — the problem or ticket this solves; link issues.
- How — only the non-obvious decisions (tricky trade-offs, rejected alternatives). Skip a file-by-file tour; the diff already shows it.
- Testing — what was actually run (commands + result), not what "should" pass.
- Risk / rollback — what could break and how to revert.
Call out anything a reviewer must look at extra carefully (migrations, auth changes, deletions).

Decision tree

Diff > ~800 lines → open with a "review order" hint (which files to read first).
Pure dependency bump → compress to What + changelog link + test evidence.
Breaking API change → put a BREAKING banner at the top with the migration step.

Done means

The description answers what/why/testing without the reviewer opening the diff, and every claim in "Testing" corresponds to a command that was actually executed.

Part of awesome-antigravity-skills. Browse more Agent Skills at orangebot.ai/skills.