Repository navigation
Add investigation types to /investigate: bug, how-it-works, available-options - #235
Merged
Merged
Conversation
Move the bug-specific approach, dispatch, analysis, validation brief, audience, and stop into references/types/bug.md, and the report layout into references/templates/bug.md with the shared evidence and validation sections in references/evidence-and-validation.md. SKILL.md keeps the shared flow, gains the Investigation Types table and type-file contract, parses a leading type token and trailing report path, announces the resolved type before dispatch, and pins where the report is written. A Bats test holds the table, type files, templates, and argument-hint in agreement.
Add the how-it-works type file and template, the detection and fit-check examples, and the how-it-works token in the argument-hint and description. Redraw the boundaries in the same commit so no two skills claim one question: research covers the open web and prior art, investigate covers questions this codebase alone can answer, and code-overview and code-walkthrough send a single how-it-works question to investigate. Add a ruby-shop eval scaffold, a how-it-works eval, and a prior-art eval that must not trigger investigate.
Mark the Bats file executable and tell shellcheck the backticks in its patterns are literal Markdown.
Add the available-options type file and template, its table row between bug and how-it-works so it wins the tie-break over how-it-works, its token in the argument-hint and description, detection examples, and an available-options eval on the ruby-shop scaffold.
Rewrite the investigate long-form doc around the bug, how-it-works, and available-options types. Update investigate-to-confluence to accept any type, pass a named type first and its /tmp report path last, and stop before implementing anything. Refresh the han-coding and han-atlassian README scent lines, the skills index, the han-coding plugin description, the workflows map, and the research-a-decision how-to.
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
/investigatenow runs as one of three investigation types:bug,how-it-works, oravailable-options. Name the type first, or leave it out and the skill picks one from the question. A named type that clearly does not fit the question gets one question asking which to use. Abugrun writes the same report sections it wrote before.han-coding/skills/investigate/references/types/(detection signals, dispatch roster, analysis steps, validator brief, audience, stop) with its own report template underreferences/templates/. The evidence and validation sections every report shares live once, inreferences/evidence-and-validation.md.SKILL.mdkeeps the shared flow and owns the only list of type tokens. Every run opens with a block naming the type, why it was chosen, the question as read, and the report path.investigation-types.batsholds the table, type files, templates,argument-hint, and description in agreement.researchcovers the open web and prior art,investigatecovers questions the codebase alone can answer, andcode-overviewandcode-walkthroughsend a single how-it-works question toinvestigate.investigate-to-confluenceaccepts every type.docs/plans/investigate-types/.Not verified yet: the new evals in
evals/investigate/have not been run, because there is notests.jsonrunner in the repo. No type has had an end-to-end trial run.Before requesting review
Do not bump the plugin version and do not edit
CHANGELOG.mdin this PR. Both are handled by the/han-releaseskill when a release is cut.han-communication/references/writing-voice.md./investigatelocally once per type and confirm each works end-to-end./han-update-documentationfrom this branch./update-pr-descriptionto write the final description.