Repository navigation
review-kit 0.3.1: name maxVerifyPerJob again, document measured resume - #18
Merged
Merged
Conversation
- whenToUse names maxVerifyPerJob again. 0.3.0 dropped it while shortening the listing entry, and a real run asked to verify up to 5 findings per reviewer launched without it, then stopped and started over. A test keeps it named. - README: the cache behaviour of a same-session resume is measured on 2.1.311 (raising maxJobs from 2 to 4 brought the planner and both earlier reviewers back cached; every verifier and the reporter ran again). - README: a resumeFromRunId relaunch goes by script path, which the Workflow(review-kit:review) rule does not approve; previous launches by name. 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
whenToUsenamesmaxVerifyPerJobagain. 0.3.0 dropped it while shortening the listing entry. In the seeded-defects real run, a prompt asking to "verify up to 5 findings per reviewer" launched without it; Claude found it in the script, stopped the run and started over. The entry is now 1,303 chars (still under the 1,400 the test allows), and a test keeps the argument named.maxJobsfrom 2 to 4 brought the planner and both earlier reviewers back from the cache; the two new reviewers, all four verifiers (three of them re-checks with unchanged prompts) and the reporter ran.resumeFromRunIdrelaunch goes by the run's script path, whichWorkflow(review-kit:review)does not match; in-pit was denied. Continuing withpreviouslaunches by name.Release checks run on 0.3.0 (2.1.311)
description + " - " + whenToUse.Test plan
node --test(182 pass)claude plugin validate --strictfor.,./review-kit,./token-audit,./token-meterclaude plugin test ./token-meter(40 pass)After merge: tag
review-kit-v0.3.1(0.3.0 stays untagged, since it shipped the regression).🤖 Generated with Claude Code