clud-bug 0.6.5 → 0.6.6

package/lib/agents-md.js

@@ -8,7 +8,12 @@ import { join } from 'node:path';
 
 const START_MARKER = '<!-- clud-bug-start -->';
 const END_MARKER   = '<!-- clud-bug-end -->';
-const BLOCK_VERSION = 'v1';
+// v2 (clud-bug v0.6.6+): trimmed from ~44 lines to ~10. Full collaboration
+// rules moved to the bundled `clud-bug-collaboration` skill (always installed
+// alongside clud-bug), which clud-bug-review loads at review time. AGENTS.md
+// becomes a pointer + the strict-mode toggle (repo-specific, varies per
+// consumer). Compounds across every agent session in every consuming repo.
+const BLOCK_VERSION = 'v2';
 
 // Files we'll touch when present, plus files we'll create if missing.
 // AGENTS.md is the cross-tool canonical (logmind made it canonical too).
@@ -43,49 +48,20 @@ const TOUCH_IF_PRESENT = [
 export function renderBlock({ version, strictMode } = {}) {
   const versionLine = version ? `_Installed at clud-bug v${version}._` : '';
   const strictNote = strictMode === true
-    ? 'Strict mode is **on** in this repo (workflow check fails on critical findings).'
-    : 'Strict mode is **off** in this repo (advisory only).';
+    ? '**on** in this repo (workflow check fails on critical findings)'
+    : '**off** in this repo (advisory only)';
   return `${START_MARKER}
 <!-- clud-bug-block-version: ${BLOCK_VERSION} -->
 ## clud-bug — Claude PR review
 
-This repository uses [clud-bug](https://cludbug.dev) to review pull requests
-automatically. Three things matter when other agents (or future-you) work
-in this repo:
+This repo uses [clud-bug](https://cludbug.dev) for automatic PR reviews.
+Full collaboration rules — fix-push flow, skill structure, comment format,
+strict-mode mechanics, workflow-edit constraint — live in the bundled
+[\`clud-bug-collaboration\` skill](.claude/skills/clud-bug-collaboration/SKILL.md).
+Read that skill before pushing fixes addressing prior review threads.
 
-### When you push fixes addressing prior Clud Bug review threads
-
-The bot resolves its own prior review threads on the next pass when it can
-verify the fix in the diff. You don't need to manually resolve threads it
-opened — push the fix, wait ~2 minutes, and check the PR. If a thread it
-left isn't auto-resolved after a fix, the bot judged the issue still open;
-read its latest review comment for what it's still flagging.
-
-### Strict mode
-
-${strictNote} Toggle by editing \`.claude/skills/.clud-bug.json\`:
-
-\`\`\`json
-{ "strictMode": true | false, ... }
-\`\`\`
-
-The setting is read from the **base ref** of any open PR, so PRs cannot
-disable strict mode on themselves. Changes take effect on PRs opened after
-they merge to the base branch.
-
-### Where the skills live
-
-Project-aware review rules live in \`.claude/skills/<name>/SKILL.md\`. A
-small baseline kit ships with every install — see
-\`.claude/skills/.clud-bug.json\` for the current set. Add more via
-\`clud-bug add <source/name>\` (from skills.sh) or by dropping your own
-\`.md\` files there. They auto-load into the reviewer.
-
-### Editing the workflow
-
-Anthropic's \`claude-code-action\` refuses to run on PRs that modify its own
-workflow file. Use \`clud-bug edit-workflow\` to bundle workflow tweaks into
-their own isolated PR — see [README](https://github.com/thrillmade/clud-bug#when-you-edit-the-workflow).
+Strict mode is ${strictNote}. Toggle via \`.claude/skills/.clud-bug.json\`
+(read from PR **base ref**, so PRs can't disable strict-mode on themselves).
 
 ${versionLine}
 ${END_MARKER}`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clud-bug",
-  "version": "0.6.5",
+  "version": "0.6.6",
   "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.5
+        uses: thrillmade/clud-bug/.github/actions/strict-mode-gate@v0.6.6
         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.5
+        uses: thrillmade/clud-bug/.github/actions/strict-mode-gate@v0.6.6
         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.5
+        uses: thrillmade/clud-bug/.github/actions/strict-mode-gate@v0.6.6
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}