review-stack-auditlisted

Use when asking whether the AI review tools still earn what we pay for them — "audit the review stack", "are we still paying for Greptile", "did a cap change", "re-check review tool costs", or the monthly check. Re-measures each tool's billed state, caps, throughput, and unique value, compares against the recorded baseline, and files drift issues. Advisory only — never edits rules.
auerbachb/claude-code-config · ★ 5 · Code & Development · score 73

Install: claude install-skill auerbachb/claude-code-config

# review-stack-audit — do the review tools still earn their keep? Issue #1199 realigned the review chain with what we actually pay for. That was a snapshot. Subscriptions lapse, caps shrink without notice, pricing moves, and new tools appear — and none of it announces itself. The last two mismatches (BugBot's spend cap, CodeAnt's "not subscribed" state) both surfaced as a bad afternoon of PRs queuing on review rather than as a line item anyone caught early. This skill is the recurring version of that check. > **ADVISORY ONLY — NON-NEGOTIABLE.** This skill **never** edits a rule, skill, > script, or config, and never changes a subscription. Not when the verdict is > obvious. Its entire output surface is a snapshot, a report, and GitHub issues. > A human lands any change through the normal issue → branch → PR flow. Billing > actions are the user's alone — this skill says "this looks like a bill with no > return", never "cancelled it for you". **Sibling to `/harness-audit`, not part of it.** That audit asks whether the harness already does natively what we automate by hand — an internal-redundancy axis. This one asks whether external spend still buys value. Same cadence, same advisory posture, same issue-filing discipline; different question. Resolve the repository locator before either engine runs: ```bash resolve_script() { local name="$1" candidate for candidate in \ "$HOME/.claude/skills-worktree/.claude/scripts/$name" \ "$HOME/.claude/scripts/$name" \