clud-bug 0.6.4 → 0.6.5

package/lib/prompts.js

@@ -212,6 +212,42 @@ On a first-time review, "resolved from prior" and "still
 open" are both 0. On follow-up reviews after a fix-push,
 "resolved from prior" should typically be positive.
 
+Stats header (required, immediately under **This round:**):
+Lead with ONE single-line stats header that uses severity emoji
+so agents re-reading this comment on a future review pass can
+triage at a glance (and skip parsing the body on the common
+zero-findings case). Three tiers:
+
+  🔴 important — bugs / security / perf / missing test coverage
+  🟡 nit       — minor suggestions, style nits, observations
+  🟣 pre-existing — issues that pre-date this PR (not its author's
+                    fault, but worth surfacing for awareness)
+
+Emit exactly this shape on the line immediately after **This round:**:
+
+  Found: N 🔴 / N 🟡 / N 🟣
+
+When all three are 0 the entire substantive body is optional —
+agents reading this header on a future re-review can stop here.
+
+Per-finding format (severity emoji + collapsible reasoning):
+Each finding in critical/minor/per-skill sections uses this
+write-time-compressed format. The summary line is the load-bearing
+claim; the long-form reasoning lives in a \`<details>\` block that
+humans expand inline (GitHub renders it natively) but future agent
+re-reads can skip token-cheaply.
+
+  🔴 [skill-name]: One-line claim (file:line).
+  <details><summary>Reasoning</summary>
+
+  Longer explanation: evidence anchors, suggested fix, edge cases.
+
+  </details>
+
+Use 🔴 for important findings (the ones strict-mode gates on),
+🟡 for nits, 🟣 for pre-existing issues. The severity emoji
+makes the finding's tier scannable without parsing prose.
+
 Per-skill scan block (required, immediately under the status line):
 After the **This round:** counters, emit a "### Per-skill scan"
 section with ONE line per loaded skill — even silent ones. This

package/lib/skills.js

@@ -537,6 +537,29 @@ export function selectReviewBody(comments, botLogin) {
 // passing — which is the right posture: if the bot didn't post a review
 // with the strict-mode header, there's nothing for the gate to fail on.
 // "Loud failure for missing manifest" is handled upstream in the composite.
+// Extract the v0.6.5+ stats header line "Found: N 🔴 / N 🟡 / N 🟣"
+// from a review comment body. Returns {important, nit, preExisting} when
+// found, null otherwise. The header lets agents reading the comment on a
+// re-review triage at a glance — on the common zero-findings case, the
+// header IS the entire substantive payload, so an ingest can short-circuit
+// without parsing the body.
+//
+// The match is intentionally permissive on whitespace around the slashes
+// and tolerates 1+ digits for each count. Severity emoji are matched
+// literally — a future bot revision that changes the emoji would break
+// this parser loudly, which is the intended behavior (catches drift).
+export function extractStatsHeader(comment) {
+  if (typeof comment !== 'string' || !comment) return null;
+  const re = /Found:\s*(\d+)\s*🔴\s*\/\s*(\d+)\s*🟡\s*\/\s*(\d+)\s*🟣/u;
+  const m = comment.match(re);
+  if (!m) return null;
+  return {
+    important: parseInt(m[1], 10),
+    nit: parseInt(m[2], 10),
+    preExisting: parseInt(m[3], 10),
+  };
+}
+
 export function isCriticalReviewHeader(headerLine) {
   if (typeof headerLine !== 'string') return false;
   return /Clud Bug review — critical findings/.test(headerLine);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clud-bug",
-  "version": "0.6.4",
+  "version": "0.6.5",
   "description": "Skill-driven Claude PR review. Ship a brand-voice skill, get brand reviews. Each finding cites the skill that motivated it. CLI installs the workflow + a baseline kit; add more from skills.sh.",
   "homepage": "https://cludbug.dev",
   "bugs": "https://github.com/thrillmade/clud-bug/issues",

package/templates/workflow-py.yml.tmpl

@@ -79,6 +79,6 @@ jobs:
       # Strict-mode gate — composite action; see workflow.yml.tmpl for design notes.
       - name: Strict mode — fail check on critical findings
         if: success()
-        uses: thrillmade/clud-bug/.github/actions/strict-mode-gate@v0.6.4
+        uses: thrillmade/clud-bug/.github/actions/strict-mode-gate@v0.6.5
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}

package/templates/workflow-ts.yml.tmpl

@@ -79,6 +79,6 @@ jobs:
       # Strict-mode gate — composite action; see workflow.yml.tmpl for design notes.
       - name: Strict mode — fail check on critical findings
         if: success()
-        uses: thrillmade/clud-bug/.github/actions/strict-mode-gate@v0.6.4
+        uses: thrillmade/clud-bug/.github/actions/strict-mode-gate@v0.6.5
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}

package/templates/workflow.yml.tmpl

@@ -130,6 +130,6 @@ jobs:
       # Letting the action's own failure fail the check is louder and right.
       - name: Strict mode — fail check on critical findings
         if: success()
-        uses: thrillmade/clud-bug/.github/actions/strict-mode-gate@v0.6.4
+        uses: thrillmade/clud-bug/.github/actions/strict-mode-gate@v0.6.5
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}