diff --git a/entry b/entry
index 1a13d59..818380b 100755
--- a/entry
+++ b/entry
@@ -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")
 
diff --git a/modes.ts b/modes.ts
index 126cb70..45fca21 100644
--- a/modes.ts
+++ b/modes.ts
@@ -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")