CLDSRV-880 Fix markdown lint errors in review-pr skill

Wrap long lines to stay under 80 chars (MD013) and use
four-backtick fence for the heredoc example so inner
suggestion fences don't trigger MD031.

Author: nicolas2bert

.claude/skills/review-pr/SKILL.md

@@ -86,16 +86,33 @@ Parse `$ARGUMENTS` to extract the repo and PR number:
 
 #### Part A: Inline file comments
 
-For each issue, post a comment on the exact file and line. Keep comments short (1-3 sentences), end with `— Claude Code`. Use line numbers from the **new version** of the file.
+For each issue, post a comment on the exact file and
+line. Keep comments short (1-3 sentences), end with
+`— Claude Code`. Use line numbers from the **new
+version** of the file.
+
+**Without suggestion block** — single-line command,
+`<br>` for line breaks:
 
-**Without suggestion block** — single-line command, `<br>` for line breaks:
 ```bash
-gh api -X POST -H "Accept: application/vnd.github+json" "repos/<owner/repo>/pulls/<number>/comments" -f body="Issue description.<br><br>— Claude Code" -f path="file" -F line=42 -f side="RIGHT" -f commit_id="<headRefOid>"
+gh api -X POST \
+  -H "Accept: application/vnd.github+json" \
+  "repos/<owner/repo>/pulls/<number>/comments" \
+  -f body="Issue description.<br><br>— Claude Code" \
+  -f path="file" -F line=42 \
+  -f side="RIGHT" -f commit_id="<headRefOid>"
 ```
 
-**With suggestion block** — use a heredoc (`-F body=@-`) so code renders correctly:
-```bash
-gh api -X POST -H "Accept: application/vnd.github+json" "repos/<owner/repo>/pulls/<number>/comments" -F body=@- -f path="file" -F line=42 -f side="RIGHT" -f commit_id="<headRefOid>" <<'COMMENT_BODY'
+**With suggestion block** — use a heredoc
+(`-F body=@-`) so code renders correctly:
+
+````bash
+gh api -X POST \
+  -H "Accept: application/vnd.github+json" \
+  "repos/<owner/repo>/pulls/<number>/comments" \
+  -F body=@- -f path="file" -F line=42 \
+  -f side="RIGHT" \
+  -f commit_id="<headRefOid>" <<'COMMENT_BODY'
 Issue description.
 
 ```suggestion
@@ -105,16 +122,22 @@ second line of suggested code
 
 — Claude Code
 COMMENT_BODY
-```
+````
 
-Only suggest when you can show the exact replacement. For architectural or design issues, just describe the problem.
+Only suggest when you can show the exact replacement.
+For architectural or design issues, just describe the
+problem.
 
 #### Part B: Summary comment
 
-Single-line command, `<br>` for line breaks. No markdown headings — they render as giant bold text. Flat bullet list only:
+Single-line command, `<br>` for line breaks. No markdown
+headings — they render as giant bold text. Flat bullet
+list only:
 
 ```bash
-gh pr comment <number> --repo <owner/repo> --body "- file:line — issue<br>- file:line — issue<br><br>Review by Claude Code"
+gh pr comment <number> --repo <owner/repo> \
+  --body "- file:line — issue<br>\
+- file:line — issue<br><br>Review by Claude Code"
 ```
 
 If no issues: just say "LGTM". End with: `Review by Claude Code`