fix(review): fix broken nested code fence in comment template

Prettier mangled the nested code fences (4-backtick outer + 3-backtick
suggestion inner). Replaced with plain-text numbered structure +
indented example. Also fixed orphaned 4-backtick fence closing Step B.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: wenshao

packages/core/src/skills/bundled/review/SKILL.md

@@ -403,28 +403,25 @@ If a finding was auto-fixed in Step 8, prefix its comment with **[Auto-fixed]**
 
 Do **not** post low-confidence findings as PR inline comments — they appear only in the terminal output under "Needs Human Review." This keeps PR comments high-signal.
 
-````
-# Step A: Use write_file tool to create /tmp/qwen-review-{target}-comment.txt
-# The EXACT content must follow this template (do NOT rewrite the footer):
+**Step A**: Use `write_file` to create `/tmp/qwen-review-{target}-comment.txt`. The content MUST follow this exact structure:
 
-{prefix} {issue description}
+1. First line: the prefix — one of `**[Critical]**`, `**[Suggestion]**`, `**[Auto-fixed][Critical]**`, or `**[Auto-fixed][Suggestion]**` — followed by the issue description.
+2. Then a blank line.
+3. Then the suggested fix. **Use a `suggestion` code block** (supported by GitHub, GitLab, Gitea, etc.) whenever the fix is a direct replacement of the commented lines — this lets the PR author accept it with one click. If the fix spans multiple locations or adds new code, use a regular code block instead.
+4. Then a blank line.
+5. Last line: the footer `_— {{model}} via Qwen Code /review_` — copy this EXACTLY, do NOT shorten or rephrase.
 
-```suggestion
-{replacement code that GitHub can apply with one click}
-````
+Example (single-line fix with suggestion block):
 
-If the fix cannot be expressed as a direct line replacement (e.g., it spans
-multiple locations or requires new code), use a regular code block instead.
+    **[Critical]** `findNextCjkWordEnd` returns `b.end` when `col < b.start`, skipping non-CJK text.
 
-_— {{model}} via Qwen Code /review_
+    ```suggestion
+        if (col < b.start) {
+          return null;
+        }
+    ```
 
-````
-
-Where `{prefix}` is one of: `**[Critical]**`, `**[Suggestion]**`, `**[Auto-fixed][Critical]**`, or `**[Auto-fixed][Suggestion]**`.
-
-**Use `suggestion` code blocks** (supported by GitHub, GitLab, Gitea, etc.) whenever the fix is a direct replacement of the commented lines. This lets the PR author accept the fix with one click. Only fall back to regular code blocks when the fix cannot be expressed as a line replacement (e.g., spans multiple locations or adds new code).
-
-⚠️ The footer `_— {{model}} via Qwen Code /review_` must appear **exactly as shown** — including the model name, "via", and "Qwen Code /review". Do NOT shorten, rephrase, or omit any part of it.
+    _— glm-5.1 via Qwen Code /review_
 
 ```bash
 # Step B: Post single-line comment referencing the file:
@@ -444,7 +441,7 @@ gh api repos/{owner}/{repo}/pulls/{pr_number}/comments \
   -F line={end_line} \
   -f start_side="RIGHT" \
   -f side="RIGHT"
-````
+```
 
 Repeat Steps A-B for each finding, overwriting the temp file each time. Clean up the temp file in Step 11.