ShockVPN/shockbot
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clean up review mode

Browse Source
This commit is contained in:
Colin McDonnell
2025-12-22 18:35:29 -08:00
parent cc59a16472
commit 72a040aafa
2 changed files with 2 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
entry
+1 -8
View File
@@ -92641,14 +92641,7 @@ ${disableProgressComment ? "" : `
3. **DRAFT** - For each inline comment, find the line in the diff. Each code line shows: \`| OLD | NEW | TYPE | CODE\`. Use the NEW line number (second column).
4. **SELF-CRITIQUE** - Before submitting, DELETE any comments that are nitpicks. Make sure you understanExamples of nitpicks to DELETE:
- Whitespace/formatting changes
- Changes to playground/scratch/test files (e.g. play.ts, scratch.ts)
- Missing docs/docstrings
- Stylistic preferences that don't affect correctness
- Anything you'd describe as "minor cleanup" or "should revert"
Only keep comments about: bugs, security issues, logic errors, API design problems, or missing edge cases. If in doubt, DELETE the comment.s
4. **FILTER COMMENTS** - Do not nitpick! Do not leave compliments that are not actionable. Do not critique the code hygiene or anything stylistic.
5. **SUBMIT** \u2014 Use ${ghPullfrogMcpName}/create_pull_request_review with:
- \`comments\`: Array of all inline comments with file paths and line numbers
modes.ts
+1 -8
View File
@@ -113,14 +113,7 @@ ${
3. **DRAFT** - For each inline comment, find the line in the diff. Each code line shows: \`| OLD | NEW | TYPE | CODE\`. Use the NEW line number (second column).
4. **SELF-CRITIQUE** - Before submitting, DELETE any comments that are nitpicks. Make sure you understanExamples of nitpicks to DELETE:
- Whitespace/formatting changes
- Changes to playground/scratch/test files (e.g. play.ts, scratch.ts)
- Missing docs/docstrings
- Stylistic preferences that don't affect correctness
- Anything you'd describe as "minor cleanup" or "should revert"
Only keep comments about: bugs, security issues, logic errors, API design problems, or missing edge cases. If in doubt, DELETE the comment.s
4. **FILTER COMMENTS** - Do not nitpick! Do not leave compliments that are not actionable. Do not critique the code hygiene or anything stylistic.
5. **SUBMIT** — Use ${ghPullfrogMcpName}/create_pull_request_review with:
- \`comments\`: Array of all inline comments with file paths and line numbers