Conversation
Detects drift between implementation and spec before committing. Compares staged diffs against spec files, surfaces decisions made in code that aren't reflected in the spec, and reconciles them through an interactive review flow. Includes coverage check subcommand for spec-to-test gap analysis. Co-Authored-By: Claude Code <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
1 participant
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
.true-up/decisions.jsonl) tracks pending/rejected decisions across invocations/use-trueup coverage) analyzes spec-to-test gaps without generating testsTest plan
/use-trueupwith staged changes and a spec file present/use-trueup coverageand verify gap report format