Critical issues only
Flags only correctness, security, and performance defects. Suppresses style nits and naming preferences that don’t change behavior.
cat. № CB-001A field naturalist for your codebase.— Cluddus bugfindii, observed crawling on every PR.
npx clud-bug init
The official anthropics/claude-code-action ships with gh pr comment disabled by default. Without an explicit --allowedTools whitelist, Claude runs through your diff, composes a thorough review, and exits without ever posting a word.
Clud Bug ships the correct workflow configuration and auto-curates skills from your repository — Next.js review patterns for a Next.js repo, FastAPI patterns for a FastAPI repo, your team’s own rules for your team’s own repo. Every PR gets a comment within ~2 minutes, shaped by skills relevant to what you actually wrote.
Flags only correctness, security, and performance defects. Suppresses style nits and naming preferences that don’t change behavior.
cat. № CB-001Every claim must quote the line under criticism. No hand-waving, no vague “might cause issues.” Cite or delete.
cat. № CB-002A code review is not a redesign. Don’t suggest patterns that fight the surrounding codebase’s established style.
cat. № CB-003Found all four planted bugs plus a fifth bonus problem (command injection via sh -c + rm -rf — worse than the SQL injection — RCE). Inline comments posted at each site.# 1. Survey the habitat, pin specimens, draft the field kit. npx clud-bug init 🐛 Field season opens in ~/your-repo. baseline kit: 3 specimens pinning specimens to .claude/skills/... pinned 3 specimens wrote .github/workflows/clud-bug-review.yml # 2. Commit the field kit and push. git add .claude .github/workflows/clud-bug-review.yml git commit -m "Add clud-bug" && git push