Skip to content

Commit 3180c38

Browse files
fa-sharpfa-sharp
authored
Merge branch 'main' into fix-middleware-leak-2
2 parents 5fb5a22 + 7e8d0ee commit 3180c38

590 files changed

Lines changed: 8962 additions & 4636 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.agents/skills/astro-pr-writer/SKILL.md‎

Lines changed: 109 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,109 @@
1+
---
2+
name: astro-pr-writer
3+
description: 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.
4+
---
5+
6+
# Astro PR Writer
7+
8+
Write Astro pull request descriptions that help reviewers quickly understand intent, behavior changes, and validation.
9+
10+
Use this skill whenever the user asks for any PR-writing task, including:
11+
12+
- create/open a pull request
13+
- create/open a draft pull request
14+
- update a PR title
15+
- update a PR body/description
16+
- write PR notes/summary
17+
18+
## Core Principle
19+
20+
Describe the **change**, **how it works**, and **why it matters**.
21+
22+
- `Changes` explains what the fix/feature does.
23+
- `Testing` explains how behavior was validated.
24+
- `Docs` explains whether user-facing docs changes are needed.
25+
26+
Do not use PR sections as a task log.
27+
28+
## PR Title Rules
29+
30+
Use a human, reviewer-friendly title.
31+
32+
- Describe the outcome in plain language.
33+
- Keep it concise and specific.
34+
- Prefer phrasing a person would naturally write in a review queue.
35+
36+
Do not use:
37+
38+
- conventional commit prefixes in PR titles (`fix:`, `feat:`, `docs:`, etc.)
39+
- scoped commit-style titles (`fix(cloudflare): ...`)
40+
41+
## Body Rules
42+
43+
Use this structure:
44+
45+
```md
46+
## Changes
47+
48+
- <Behavior change and why it matters>
49+
- <Implementation detail and impact>
50+
51+
## Testing
52+
53+
- <What scenarios were validated and why this proves the behavior>
54+
- <Key test file/test name where applicable>
55+
56+
## Docs
57+
58+
- <No docs update needed, because ...>
59+
```
60+
61+
### Changes
62+
63+
Focus on behavior, implementation approach, and impact.
64+
65+
Include:
66+
67+
- what now works that did not work before
68+
- how the fix/feature works (reviewer-useful level)
69+
- user-facing reliability/compatibility/perf behavior changes
70+
71+
Do not include:
72+
73+
- "added test" or "updated fixture" (belongs in `Testing`)
74+
- "added changeset"
75+
- internal process notes with no behavior impact
76+
77+
### Testing
78+
79+
Explain validation quality.
80+
81+
Include:
82+
83+
- scenarios validated (happy path, failure path, regression)
84+
- why those checks prove correctness
85+
- key test references
86+
87+
Do not include:
88+
89+
- command transcript lists
90+
91+
### Docs
92+
93+
Explain docs impact clearly.
94+
95+
- If docs are not needed, say why in one sentence.
96+
- If docs are needed, link the docs PR.
97+
98+
## Brevity Guidance
99+
100+
- Keep simple PRs short (1-2 bullets per section can be enough).
101+
- Add detail only when it helps reviewer understanding.
102+
- Avoid repeating the same point across sections.
103+
104+
## Self-Check Before Posting
105+
106+
- Title is reviewer-friendly (not commit-style)
107+
- `Changes` bullets describe behavior/implementation/impact
108+
- `Testing` explains scenarios and outcomes, not shell commands
109+
- `Docs` decision is explicit

‎.agents/skills/triage/comment.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Generate and return a GitHub comment following the template below.
3636
The **Fix** line in the template has three possible forms. Choose the one that matches the triage outcome:
3737

3838
1. **You created a fix:** Use `I was able to fix this issue.` and include the suggested fix link.
39-
2. **The issue is already fixed on main** (e.g. the user is on an older major version and the bug doesn't reproduce on current main): Use `This issue has already been fixed.` and tell the user how to get the fix (e.g. upgrade). Link the relevant upgrade guide if applicable: [v6](https://v6.docs.astro.build/en/guides/upgrade-to/v6/), [v5](https://docs.astro.build/en/guides/upgrade-to/v5/).
39+
2. **The issue is already fixed on main** (e.g. the user is on an older major version and the bug doesn't reproduce on current main): Use `This issue has already been fixed.` and tell the user how to get the fix (e.g. upgrade). Link the relevant upgrade guide if applicable: [v6](https://docs.astro.build/en/guides/upgrade-to/v6/), [v5](https://docs.astro.build/en/guides/upgrade-to/v5/).
4040
3. **You could not find or create a fix:** Use `I was unable to find a fix for this issue.` and give guidance or a best guess at where the fix might be.
4141

4242
### "Priority" Instructions

‎.changeset/adapter-interface-breaking.md‎

Lines changed: 0 additions & 11 deletions
This file was deleted.

‎.changeset/astro-ssr-check-metadata.md‎

Lines changed: 0 additions & 5 deletions
This file was deleted.

‎.changeset/beige-clowns-read.md‎

Lines changed: 0 additions & 5 deletions
This file was deleted.

‎.changeset/beta-tag-alpinejs.md‎

Lines changed: 0 additions & 5 deletions
This file was deleted.

‎.changeset/beta-tag-check.md‎

Lines changed: 0 additions & 5 deletions
This file was deleted.

‎.changeset/beta-tag-create-astro.md‎

Lines changed: 0 additions & 5 deletions
This file was deleted.

‎.changeset/beta-tag-db.md‎

Lines changed: 0 additions & 5 deletions
This file was deleted.

‎.changeset/beta-tag-language-server.md‎

Lines changed: 0 additions & 5 deletions
This file was deleted.

0 commit comments

Comments
 (0)