Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/explain-diff
Explain a diff, branch, PR, patch, or review packet; use after Full-path verification when the change teaches a useful business or technical concept.
Passed 10 of 19 test cases with the skill, and 10 of 19 without it.
3 fixed8 passed either way8 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm passing `--visual` to inspect a complex state machine update. Which directory on the file system is allowed for generating temporary diagram assets?
| Checked | Without skill | With skill |
|---|---|---|
| Restricts visual artifact generation to the system temp directory | Missed | Passed |
The instructions your model reads when the skill loads.
Transfer ownership of a change. Manual mode is repository-read-only; --visual may write only to the system temp directory.
Parse --visual; the rest is a working tree, branch, range, PR, patch, or packet. Default to the current worktree. Use the available request, plan, chronicle, verification, and details about what was not checked. Do not require a standard packet.
In Full, require the request, plan or chronicle, diff, fresh Verify results, and details about what was not checked. Otherwise inspect read-only.
State verification status. With absent or stale evidence, label Unverified change and separate code facts from unproved behavior.
For --visual, read visual mode. At the automatic Full checkpoint, name the dynamic concept a visual would clarify and ask Continue in chat or Create visual; only the latter activates it.
Assume no project knowledge. Present only what the change needs:
Use a small diagram only when clearer than prose.
Merge overlapping concepts and omit filler. Zero questions is valid. Cover relevant business rules, invariants, flows, states, edge cases, architecture, lifecycle, concurrency, trade-offs, failure modes, and evidence—not syntax.
Ask one applied free-response question at a time through AskUserQuestion. Show the text box with I don't know — explain and Proceed without answering, translated to the conversation language. Do not offer answer choices. In the question text, invite the user to answer in the free-text box; never name interface internals such as "Other".
If the interface cannot show selectable actions, list those two actions beside the free-response prompt.
test cases passed, vs 10 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.