Repository navigation
review-kit 0.5.0: cost estimate, measured budget, shorter listing entry - #20
Merged
Merged
Conversation
- A needs-confirmation stop carries an estimate of agents and tokens (likely and worst case) for the pairs in wouldRun and for all pairs, and next tells the caller to show it. The constants are per-agent averages from a real 62-pair run. - Token-budget sizing uses measured output per agent and follows votes, maxVerifyPerJob and verify: 16k per job at the defaults instead of a flat 25k, so "+500k" runs 29 jobs instead of 19. - whenToUse is shorter and points one-branch or one-PR reviews at /code-review. The listing entry is 932 chars, down from 1,366; a test keeps it under 993, half of 0.2.2's 1,986. - README: "When to use which", the estimate, the re-derived token budget, measured run costs and reviewer-model advice. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
needs-confirmationstop now carriesestimate: the likely and worst-case agents and tokens for the pairs inwouldRunand for all pairs.nexttells the caller to show it when asking the user.+500k-style budget uses measured output per agent (4k per reviewer, 2k per verifier, 25k fixed) and now followsvotes,maxVerifyPerJobandverify. A job costs 16k at the defaults instead of a flat 25k, so+500kruns 29 jobs instead of 19.whenToUsedrops each argument's shape (thebad-argsmessages already give it) and points one-branch or one-PR reviews at/code-review.claude plugin detailsreports ~152 tokens because it counts only the agents./contextputs the agents at 169 and an installed 0.3.1 entry (1,303 chars) at ~440–460 tokens. The 0.5.0 entry works out to ~320 tokens at the same ratio (derived, not measured).model: { reviewer: "opus" }for a release gate, the defaults for routine sweeps.Eval (2.1.312, one real run)
The shorter
whenToUsecould stop the workflow being picked, so the seeded-defects case ran once as a real session against this branch: 11/12 graders,workflow-usedpassed (one Workflow call with matching input), 5/5 defects and 1/4 decoys confirmed, 119 s, $1.84. The decoy count is within 0.4.0's range on the default models.Test plan
node --test(206 pass)claude plugin validate --strictfor.,./review-kit,./token-audit,./token-meterclaude plugin test ./token-meter(40 pass)After merge: tag
review-kit-v0.5.0with notes from the changelog, then confirm the listing figure with/contexton an installed 0.5.0.🤖 Generated with Claude Code