Help us improve
Share bugs, ideas, or general feedback.
From consensus-loop
Manually runs consensus-loop audits reviewing pending trigger_tag items in watch files. Use to trigger audits without editing files, re-run failures, test prompts, with dry-run, auto-fix, and model options.
npx claudepluginhub berrzebb/claude-plugins --plugin consensus-loopHow this skill is triggered — by the user, by Claude, or both
Slash command
/consensus-loop:auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the audit process manually.
Guides writing evidence packages for consensus-loop watch file in code reviews. Covers claims, changed files, executable tests, results, risks, tag lifecycles, and rejection fixes.
Audits .claude/ config for cross-references, permissions, inventory drift, model tiers, docs freshness. Auto-fixes issues at high/medium/all severity levels or upgrades with verification and A/B testing.
Audits Claude Code hooks for config validity, script structure, matchers, env vars, decisions, and tests. Run after hook creation, before releases, or for periodic checks.
Share bugs, ideas, or general feedback.
Run the audit process manually.
node ${CLAUDE_PLUGIN_ROOT}/audit.mjs {{ arguments }}
Read the respond file (gpt.md) and summarize:
| Flag | Effect |
|---|---|
--dry-run | Print audit prompt without executing |
--no-resume | Fresh session (don't resume previous) |
--auto-fix | Auto-correct via Claude CLI after audit |
--model <name> | Model override (default: gpt-5.4) |
--reset-session | Delete saved session before running |
--watch-file <path> | Override watch file path (worktree support) |