Snippets had no field for free text, so explanations ended up in when_to_use. That text is the trigger, and it is joined onto every chunk the snippet is embedded as. Write-ups of up to 3 KB were found there.
notes is stored after the code under ## Notes and parsed back from the body. It is carried through by update, merge and un-merge. A snippet with no notes produces the same body byte for byte, so nothing re-embeds.
MCP create_snippet and update_snippet take notes. They return trigger_advice when when_to_use is long, has headings, or runs to several paragraphs.
Tool docs, the reusing-code skill and the editor hint describe the trigger as the situation. The editor gains a Notes field, and the detail view renders notes as markdown.
Snippets had no field for free text, so explanations ended up in `when_to_use`. That text is the trigger, and it is joined onto every chunk the snippet is embedded as. Write-ups of up to 3 KB were found there.
- `notes` is stored after the code under `## Notes` and parsed back from the body. It is carried through by update, merge and un-merge. A snippet with no notes produces the same body byte for byte, so nothing re-embeds.
- MCP `create_snippet` and `update_snippet` take `notes`. They return `trigger_advice` when `when_to_use` is long, has headings, or runs to several paragraphs.
- Tool docs, the reusing-code skill and the editor hint describe the trigger as the situation. The editor gains a Notes field, and the detail view renders notes as markdown.
- Plugin version is 2026.09.23.2127.
CI run 7403 on 4ae18a9: all six jobs green.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
A snippet had no field for prose, so what a session learned about one went
into when_to_use — the trigger joined onto every chunk it is embedded as. A
sweep found write-ups of up to 3 KB there, headings and all.
- notes: stored after the code under `## Notes`, parsed back from the body,
carried by every path that rebuilds it (update, merge, un-merge). A
snippet with no notes composes the body it always did.
- create/update_snippet (MCP) take notes and return trigger_advice when
when_to_use is long, headed or multi-paragraph. Advice, not a refusal.
- Tool docs, the reusing-code skill and the editor hint describe the trigger
as the situation and point the explanation at notes.
- Editor gains a Notes field; the detail view renders it as markdown.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Snippets had no field for free text, so explanations ended up in
when_to_use. That text is the trigger, and it is joined onto every chunk the snippet is embedded as. Write-ups of up to 3 KB were found there.notesis stored after the code under## Notesand parsed back from the body. It is carried through by update, merge and un-merge. A snippet with no notes produces the same body byte for byte, so nothing re-embeds.create_snippetandupdate_snippettakenotes. They returntrigger_advicewhenwhen_to_useis long, has headings, or runs to several paragraphs.CI run 7403 on
4ae18a9: all six jobs green.🤖 Generated with Claude Code