Skip to content

Stop wrapping review prose in code fences #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MichaelFisher1997 merged 1 commit into from
Sep 14, 2026
Merged

Stop wrapping review prose in code fences #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions .github/prompts/pr-review.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,7 @@ $PREVIOUS_REVIEWS
2. **ACKNOWLEDGE FIXES:** If a previously reported issue has been fixed, state "✅ **[FIXED]** Previous issue: [brief description]" in the appropriate section.
3. **ONLY REPORT NEW/UNRESOLVED ISSUES:** Do NOT re-report issues that have already been fixed. Only report issues that are still present in the current code.
4. **TRACK CHANGES:** If an issue was reported in a previous review but the code has changed, verify the new code and report the issue with updated file:line references if it still exists.
5. **FORMATTING:** Never wrap review prose (issue descriptions, impacts, summaries, metadata) in code fences — only wrap actual code. Use a fenced code block solely for real code snippets and tag it with the correct language (e.g. `gdscript`).

---

Expand All @@ -65,14 +66,15 @@ Then provide 2-3 sentences summarizing the PR purpose, scope, and overall qualit

Only report NEW critical issues that could cause crashes, security vulnerabilities, data loss, or major bugs.

For each issue, use this exact format:
```
For each issue, output this exact structure directly as Markdown — do not wrap it in a code fence:

**[CRITICAL]** `File:Line` - Issue Title
**Confidence:** High|Medium|Low (how sure you are this is a real problem)
**Description:** Clear explanation of the issue
**Impact:** What could go wrong if merged
**Suggested Fix:** Specific code changes needed
```

Only put actual code snippets inside the **Suggested Fix** (or the description) in a fenced block, tagged `gdscript` when it is GDScript.

## ⚠️ High Priority Issues (Should Fix)
Same approach as Critical - check previous reviews first, acknowledge fixes, only report unresolved issues.
Expand Down
Loading