Conversation
…ication, and broader autofix Addresses three gaps in the document-review skill's autofix and presentation pipeline based on real-world feedback where 12 findings were presented sequentially at equal weight despite most being obvious or mechanical: - Expand autofix_class to include completeness corrections (wrong counts, missing list entries) and add a batch_confirm tier for obvious fixes that touch meaning but have one clear answer — reducing N interactions to 1 - Add finding_type (error vs omission) so reviewers distinguish design tensions from missing mechanical steps, and presentation groups them separately within each severity level - Ensure synthesized findings (residual promotions, contradiction resolutions) always have finding_type assigned - Add cross-platform interaction instructions to batch-confirm step
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
The document-review skill presented all findings sequentially at equal weight, even when most were obvious mechanical fixes. This came from real-world feedback where a review produced 12 findings that could have been 3 interactions.
Three changes to the autofix and presentation pipeline:
Broader autofix scope —
autonow covers completeness corrections (wrong counts, missing list entries, broken cross-references) where the correct value is verifiable from the document itself, not just terminology and formatting.batch_confirmtier — New routing class betweenautoandpresent. Obvious fixes that touch document meaning but have one clear correct answer get grouped for a single yes/no/select approval instead of individual presentation. Demotion chain:automissingsuggested_fixdemotes tobatch_confirm,batch_confirmmissingsuggested_fixdemotes topresent.finding_typeclassification — New required field (errorvsomission) so the skill distinguishes design tensions from missing mechanical steps. Findings are sub-grouped within each severity level (errors first, omissions second), and the summary line reports both counts. Synthesized findings (residual promotions, contradiction resolutions) always get afinding_typeassigned.Files changed
SKILL.md— Phase 3.4-3.7 synthesis rules, Phase 4 presentation flowfindings-schema.json—batch_confirmenum,finding_typefield and metadatasubagent-template.md— Reviewer instructions for new fieldsreview-output-template.md— Example output with batch confirm section, error/omission grouping, expanded coverage table🤖 Generated with Claude Opus 4.6 (1M context, extended thinking) via Claude Code