clud-bug-collaborationlisted

# Working in a clud-bug-installed repo Clud Bug reviews every PR via `anthropics/claude-code-action`. As another Claude Code agent working alongside it, here's what to know — these aren't arbitrary rules, they're the consequences of how the gate is wired. ## When you push fixes to a clud-bug-reviewed PR The bot reviews on `pull_request: synchronize` (every push). When you push a commit that addresses an issue Clud Bug flagged in a prior review, the bot will re-review the PR within ~2 minutes and **resolve its own prior unresolved inline review threads** where the flagged issue is verifiably fixed in the current diff. You don't have to resolve threads manually. If a thread it left isn't auto-resolved after your fix: - The bot judged the issue still open (read its latest comment for why). - Or the resolution call hit a transient API issue (re-push to retry). Don't manually resolve clud-bug threads on its behalf. The check (`required_conversation_resolution` branch protection) will block merge if unresolved threads remain — and the right fix is usually "fix the actual issue and re-push," not "mark the conversation resolved." ## When you read the PR's `clud-bug-review` check status - **Green** = Clud Bug ran and either found no critical issues OR strict mode is off (advisory). - **Red** = either the action errored OR strict mode is on AND Clud Bug flagged a critical issue. Read the latest `## 🐛 Clud Bug review` comment on the PR — the body indicates "critical findin