feat: add verify-bug skill and suspected-bug friction to whiteboard - #10
Merged
Merged
Conversation
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.
Adds
verify-bugto thedevelopmentplugin and asuspected-bugfriction type towhiteboard.verify-bug
Decides whether claimed bugs are real. It never hunts for new bugs and never fixes code.
suspected-bugentries from awhiteboardmap, pasted findings, review comments, or GitHub issues — normalized into one claim record (scenario, receipt, severity-if-true, verdict slot).confirmed (reproduced),confirmed (static),refuted, orunclear. Falls back to sequential roles without subagents.git worktreeunder.verify/, saves it as a patch, and removes the worktree. The working tree is never touched. Asks before anything beyond the repo's own test command..verify/<date>-<slug>.mdreport (excluded via.git/info/exclude), in-place verdicts for map entries, and draft GitHub replies posted only after explicit confirmation.The Prover/Skeptic/Referee structure is borrowed as an idea from existing adversarial bug-hunt skills; no text is copied.
whiteboard
suspected-bugfriction type. Entries must name a concrete triggering scenario and start asverdict: unverified; whiteboard never investigates them.adversarialdefense questions; unverified or unclear ones are asked but not graded.Checks
Ran locally:
npm run format:check,npm run validate, andnpm run sync(mirror underskills/included).