chore: format issue-review.md

Author: penalosa

.github/skills/issue-review.md

@@ -69,9 +69,11 @@ Recommend **CLOSE** (state_reason: `completed`) if, based on references within t
 When closing, cite the specific PR number and release version if known.
 
 **Template:**
+
 > This issue has been fixed in PR #XXXX, which was released in **wrangler X.Y.Z** (or the relevant package version). Please update and let us know if you're still seeing the issue.
 
 Or for older issues where the fix can't be pinpointed:
+
 > This is a fairly old issue, and from testing with the latest version, it appears to have been resolved. I'm going to close it for now — if you're still running into problems on the latest version, feel free to open a new issue with more details and we can investigate further.
 
 #### 2d: Duplicate
@@ -81,9 +83,11 @@ Recommend **CLOSE** (state_reason: `not_planned`) if a comment or linked referen
 When closing, link to the canonical issue.
 
 **Template:**
+
 > Closing as a duplicate of #XXXX. Please follow that issue for updates.
 
 If the duplicate is in another repo:
+
 > I'm closing this as a duplicate of <owner/repo>#XXXX, which is where this is being tracked.
 
 #### 2e: Not workers-sdk / Wrong Repo
@@ -98,14 +102,17 @@ Recommend **CLOSE** (state_reason: `not_planned`) if:
 **Templates:**
 
 For framework issues:
+
 > It looks like this issue is coming from <framework>, rather than from workers-sdk. I'd recommend opening an issue on that project's repo: <link>. If it turns out to be a workers-sdk issue after all, feel free to open a new issue here with more details.
 
 For runtime issues:
+
 > This looks like a Workers runtime issue rather than a tooling issue. The right place to track this is [cloudflare/workerd](https://github.com/cloudflare/workerd) so I've moved the issue there.
 
 (Set Action field to: "Transfer to cloudflare/workerd, then post this comment.")
 
 For account/support issues:
+
 > Unfortunately, we're unable to provide support for account-level issues via GitHub. Please contact Cloudflare Support at https://dash.cloudflare.com/?to=/:account/support or the email address mentioned in the error message.
 
 #### 2f: Stale / No Response
@@ -117,9 +124,11 @@ Recommend **CLOSE** (state_reason: `not_planned`) if:
 - A maintainer asked for a reproduction or clarification and the reporter never responded
 
 **Template:**
+
 > We haven't heard from you in a while so I'm going to close this issue for now. If you're still running into problems, feel free to open a new issue with more details and we can investigate further.
 
 For very old issues:
+
 > This is a very old issue so I'm going to close it for now. If you're still running into problems on the latest version, feel free to comment with more details and we can investigate further.
 
 #### 2g: Transient Platform Issue
@@ -131,9 +140,11 @@ Recommend **CLOSE** (state_reason: `completed`) if:
 - The error is from Cloudflare's API (not from Wrangler itself) and there's no way to fix it in workers-sdk
 
 **Template:**
+
 > This was a transient API issue, and should be resolved now. If you're still seeing this error, please open a new issue with the latest details and we can investigate further.
 
 Or for old transient issues:
+
 > This appears to have been a transient server-side API issue. Similar reports were caused by Cloudflare API incidents that have since been resolved. I'm going to close this for now.
 
 #### 2h: User Error / Misunderstanding
@@ -147,6 +158,7 @@ Recommend **CLOSE** (state_reason: `not_planned`) if:
 When closing, explain the correct approach and link to relevant documentation. Be helpful, not dismissive.
 
 **Template:**
+
 > This isn't a bug — <brief explanation of the correct behavior>. You can find more details in the docs: <link>. I'm going to close this for now, but feel free to ask on our [Discord](https://discord.cloudflare.com) if you have more questions.
 
 #### 2i: Breaking Change
@@ -160,6 +172,7 @@ The issue should remain open as a tracking item. Do not close it — the team ha
 **Suggested labels:** `breaking change`
 
 **Template:**
+
 > Changing this behavior at this stage would be a breaking change, so it will need to wait for the next major version. I've added the `breaking change` label to track this.
 
 (Set Action field to: "Apply `breaking change` label, then post this comment.")
@@ -175,9 +188,11 @@ Recommend **CLOSE** (state_reason: `not_planned`) if:
 **Templates:**
 
 For design decisions:
+
 > This is intentional behavior — <brief explanation>. I don't think we're likely to change this in the near future, but we appreciate the feedback.
 
 For feature requests that won't happen:
+
 > Thanks for the suggestion. We don't intend to implement this right now, but it may be revisited in future. <Optional: brief explanation of why, or pointer to an alternative approach.>
 
 #### 2k: Feature Superseded / Deprecated
@@ -189,6 +204,7 @@ Recommend **CLOSE** (state_reason: `completed`) if:
 - A newer feature or package addresses the underlying need
 
 **Template:**
+
 > This has been addressed by <feature/package>. <Brief explanation of how it solves the original request.> I'm going to close this for now.
 
 ### Step 3: Check for Insufficient Information
@@ -201,7 +217,9 @@ If the issue wasn't caught by Step 2, recommend **NEEDS MORE INFO** if:
 - The error message is missing or truncated
 
 **Template:**
+
 > Thanks for reporting this. Could you provide <specific missing information>? In particular:
+>
 > - <specific question 1>
 > - <specific question 2>
 >
@@ -215,27 +233,27 @@ If the issue wasn't caught by Step 2, recommend **NEEDS MORE INFO** if:
 
 Map the issue to a package based on labels, title, and body content:
 
-| Signal | Package |
-|---|---|
-| `wrangler` label, wrangler CLI commands, `wrangler.toml`/`wrangler.json` | `packages/wrangler` |
-| `miniflare` label, local dev simulation | `packages/miniflare` |
-| `d1` label, D1 database, `d1 execute`, migrations | `packages/wrangler` (D1 code is in wrangler) |
-| `vitest` label, worker tests, `vitest-pool-workers` | `packages/vitest-pool-workers` |
-| `vite-plugin` label, vite dev, `@cloudflare/vite-plugin` | `packages/vite-plugin-cloudflare` |
-| `c3` label, `create-cloudflare`, project scaffolding | `packages/create-cloudflare` |
-| `pages` label, Pages deployment, `_routes.json`, `_headers` | `packages/wrangler` (Pages code is in wrangler) |
-| `Workers + Assets` label, static asset serving | `packages/wrangler` |
-| `containers` label, container registry | `packages/wrangler` |
-| `workflows` label, Workflows API | `packages/wrangler` |
-| `workers-builds` label | Workers Builds (may be internal) |
-| `python` label, Python Workers | `packages/wrangler` |
-| `workers for platforms` label, dispatch namespaces | `packages/wrangler` |
-| `kv-asset-handler` label | `packages/kv-asset-handler` |
-| `types` label, `wrangler types` command | `packages/wrangler` |
-| R2, KV, Queues, Durable Objects, Vectorize bindings | `packages/wrangler` |
-| `node compat`/`nodejs compat` label, Node.js APIs | May be workerd or wrangler depending on context |
-| Workers runtime behavior (not tooling) | Likely belongs in cloudflare/workerd |
-| Cloudflare dashboard, API behavior | Likely a platform issue, not workers-sdk |
+| Signal                                                                   | Package                                         |
+| ------------------------------------------------------------------------ | ----------------------------------------------- |
+| `wrangler` label, wrangler CLI commands, `wrangler.toml`/`wrangler.json` | `packages/wrangler`                             |
+| `miniflare` label, local dev simulation                                  | `packages/miniflare`                            |
+| `d1` label, D1 database, `d1 execute`, migrations                        | `packages/wrangler` (D1 code is in wrangler)    |
+| `vitest` label, worker tests, `vitest-pool-workers`                      | `packages/vitest-pool-workers`                  |
+| `vite-plugin` label, vite dev, `@cloudflare/vite-plugin`                 | `packages/vite-plugin-cloudflare`               |
+| `c3` label, `create-cloudflare`, project scaffolding                     | `packages/create-cloudflare`                    |
+| `pages` label, Pages deployment, `_routes.json`, `_headers`              | `packages/wrangler` (Pages code is in wrangler) |
+| `Workers + Assets` label, static asset serving                           | `packages/wrangler`                             |
+| `containers` label, container registry                                   | `packages/wrangler`                             |
+| `workflows` label, Workflows API                                         | `packages/wrangler`                             |
+| `workers-builds` label                                                   | Workers Builds (may be internal)                |
+| `python` label, Python Workers                                           | `packages/wrangler`                             |
+| `workers for platforms` label, dispatch namespaces                       | `packages/wrangler`                             |
+| `kv-asset-handler` label                                                 | `packages/kv-asset-handler`                     |
+| `types` label, `wrangler types` command                                  | `packages/wrangler`                             |
+| R2, KV, Queues, Durable Objects, Vectorize bindings                      | `packages/wrangler`                             |
+| `node compat`/`nodejs compat` label, Node.js APIs                        | May be workerd or wrangler depending on context |
+| Workers runtime behavior (not tooling)                                   | Likely belongs in cloudflare/workerd            |
+| Cloudflare dashboard, API behavior                                       | Likely a platform issue, not workers-sdk        |
 
 ### Step 5: Assess Reproducibility and Severity
 
@@ -311,12 +329,13 @@ duplicate candidates. Only include what's relevant.>
 
 > <The exact comment to post on the issue. Follow the templates above for the
 > matching closure category. Key principles:
+>
 > - Always offer an escape hatch ("feel free to open a new issue")
 > - Link to specific PRs, releases, or docs when available
 > - Be concise for straightforward closures, detailed for design decisions
 > - Never be dismissive or snarky, even for spam (just close silently) or user error
 > - For NEEDS MORE INFO, ask specific questions (not generic "please provide more details")
-> Omit this section entirely for spam (close without comment) or if no comment is needed.>
+>   Omit this section entirely for spam (close without comment) or if no comment is needed.>
 ```
 
 ### Output Step 2: Write Summary File