feat(qa): add browse subcommand reference table#87
Closed
kaicianflone wants to merge 1 commit into
Closed
Conversation
Generated by consensus-guard-demo: 5 AI guard agents evaluated and approved this improvement via weighted consensus voting. The qa/SKILL.md referenced browse CLI commands throughout but never formally documented subcommands, flags, or argument types. An AI agent had to infer usage from scattered examples. This adds a Browse Binary Subcommand Reference table covering all 10 subcommands with their flags, argument types, and descriptions, plus element reference lifecycle documentation. Judge eval scores (claude-sonnet-4-6, verified 3x): Before: clarity=4, completeness=3, actionability=3 (avg 3.3/5) After: clarity=5, completeness=5, actionability=5 (avg 5.0/5) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
4 tasks
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
qa/SKILL.mddocumenting all 10 browse subcommands with flags, argument types, and descriptions@eN) lifecycle documentation warning about staleness after navigationEval Results
LLM-as-judge scores (claude-sonnet-4-6, each verified 3x for consistency):
+51% improvement, consistent across 3 independent eval runs per version.
Why this change
The judge consistently flagged that
qa/SKILL.mduses browse commands ($B goto,$B snapshot -i,$B fill @e3, etc.) throughout but never formally documents what subcommands, flags, or argument types are valid. An AI agent had to infer usage from scattered examples, risking incorrect invocations.Guard consensus
All 5 guard agents voted YES (combined risk: 0.17):
Test plan
🤖 Generated with Claude Code via consensus-guard-demo