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

Clean up PR prompt

Browse Source
This commit is contained in:
Colin McDonnell
2025-12-22 15:01:42 -08:00
parent 17ad3bd0e7
commit 615a3bc8e1
2 changed files with 5 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
entry
+3 -4
View File
@@ -83328,7 +83328,7 @@ function query({
// package.json
var package_default = {
name: "@pullfrog/action",
version: "0.0.153",
version: "0.0.154",
type: "module",
files: [
"index.js",
@@ -92644,9 +92644,8 @@ ${disableProgressComment ? "" : `
- Draft the comment text
5. **SELF-CRITIQUE** - Before submitting, review your draft:
- Remove nitpicks unless the user explicitly told you to be nitpicky. Nitpicks may include: requesting documentation/docstrings/JSDoc, commenting on minor code/whitespace formatting, commenting on small changes unrelated to the main changes.
- Ensure each comment is actionable - would the author know exactly what to do?
- Would the codebase maintainer care about this feedback?
- DO NOT NITPICK. Do not comment on minor formatting changes, changes to playground/scratch files, lack of docs/docsstrings, or small changes that seem irrelevant. Assume these things are intentional by the PR author.
- DO NOT LEAVE USELESS OR NON-ACTIONABLE COMMENTS. Compliments are not actionable.
- If you have approach-level concerns, consider whether implementation-level comments are worth including
- For issues appearing in multiple places, keep only the FIRST occurrence and reference others (e.g., "also at lines X, Y")
modes.ts
+2 -3
View File
@@ -116,9 +116,8 @@ ${
- Draft the comment text
5. **SELF-CRITIQUE** - Before submitting, review your draft:
- Remove nitpicks unless the user explicitly told you to be nitpicky. Nitpicks may include: requesting documentation/docstrings/JSDoc, commenting on minor code/whitespace formatting, commenting on small changes unrelated to the main changes.
- Ensure each comment is actionable - would the author know exactly what to do?
- Would the codebase maintainer care about this feedback?
- DO NOT NITPICK. Do not comment on minor formatting changes, changes to playground/scratch files, lack of docs/docsstrings, or small changes that seem irrelevant. Assume these things are intentional by the PR author.
- DO NOT LEAVE USELESS OR NON-ACTIONABLE COMMENTS. Compliments are not actionable.
- If you have approach-level concerns, consider whether implementation-level comments are worth including
- For issues appearing in multiple places, keep only the FIRST occurrence and reference others (e.g., "also at lines X, Y")