Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add LichAmnesia/awesome-antigravity-skills --skill pr-descriptiongit clone --depth 1 https://github.com/LichAmnesia/awesome-antigravity-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/lichamnesia/awesome-antigravity-skills/pr-description)<a href="https://agentmods.dev/skills/lichamnesia/awesome-antigravity-skills/pr-description"><img src="https://agentmods.dev/badge/skills/lichamnesia/awesome-antigravity-skills/pr-description/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lichamnesia/awesome-antigravity-skills/pr-description"><img src="https://agentmods.dev/badge/skills/lichamnesia/awesome-antigravity-skills/pr-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.00416 |
| Opus 5 | $0.00017 | $0.00208 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
pr-description scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
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.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 43 lines · 34 tokens per session scan A 5ff4e1841d5b
pr-description is a skill published in the GitHub repository LichAmnesia/awesome-antigravity-skills (7 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 34 tokens to every session and 416 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gh-address-comments
Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging…
git-pr-review
Generate a concise and structured PR description from commit history with minimal token usage.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
git-pr-workflows-git-workflow
Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g.
git-pr-workflows-pr-enhance
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensu.