Write and update Astro pull requests with reviewer-friendly titles and high-signal bodies. Trigger whenever the user asks to create a PR, open a PR, draft a PR, update PR title/body, or write PR notes/summary/description.
SkillScore100Maintained
Automatic
◆Coding pack
Last verified 9/27/2026
What it changes
Passed 23 of 23 test cases with the skill, and 6 of 23 without it.
Without skill26%
With skill100%
Checks it passed that the model alone missed
The body uses ## Changes as a section header.
The response uses ## Changes as a section header.
The response includes ## Docs as a section header.
and 26 more in the full report
17 fixed6 passed either way0 still failing0 broke
Pass-rate lift
+74 pp
Tokens
+74%
Agent turns
0%
Response time
-23%
Model gemini-3.6-flashMeasured 9/27/2026v123 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 17
Prompt
Write a summary update for an ongoing pull request that fixes image optimization memory leaks in `@astrojs/image`. We added `test/memory-leak.test.ts` and no docs changes are needed.
What was checked, without and with the skill
Checked
Without skill
With skill
The response uses ## Changes rather than ## Summary as the section header.
Missed
Passed
The response includes ## Docs as a section header.
Missed
Passed
case-22 · gemini-3.6-flash · 9/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md127 linessingle file
Astro PR Writer
Write Astro pull request descriptions that help reviewers quickly understand intent, behavior changes, and validation.
Use this skill whenever the user asks for any PR-writing task, including:
create/open a pull request
create/open a draft pull request
update a PR title
update a PR body/description
write PR notes/summary
Core Principle
Describe the change, how it works, and why it matters.
Changes explains what the fix/feature does.
Testing lists what test code was added or changed.
Docs explains whether user-facing docs changes are needed.
Do not use PR sections as a task log.
PR Title Rules
Use a human, reviewer-friendly title.
Describe the outcome in plain language.
Keep it concise and specific.
Prefer phrasing a person would naturally write in a review queue.
Do not use:
conventional commit prefixes in PR titles (fix:, feat:, docs:, etc.)
How to write JSDoc (/** */) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users. Use whenever writing or editing comments in .ts/.js source, including comments added incidentally while fixing bugs or building features. Does not cover the @docs-generated config/error reference.