From 873e6e8f88ef1dc396ca42b9316c04a6336114be Mon Sep 17 00:00:00 2001 From: Brummel Date: Mon, 1 Jun 2026 16:33:32 +0200 Subject: [PATCH] docs(issue): encourage concrete code examples as evidence MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Rule 2 (validated-or-flagged) now suggests dropping in a fenced code snippet where it sharpens the point — the input that triggers the failure or the call as it should behave — preferred over a prose paraphrase. Co-Authored-By: Claude Opus 4.8 (1M context) --- issue/SKILL.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/issue/SKILL.md b/issue/SKILL.md index 0858c99..e88a954 100644 --- a/issue/SKILL.md +++ b/issue/SKILL.md @@ -50,6 +50,15 @@ These apply to every issue, on create and on edit. `parser.rs:84` and the repro below." - Flagged: "Claim (unverified): the regression likely landed in 0b96983; not yet bisected." + - Where it sharpens the point, drop in a concrete code example — + the snippet that triggers the failure, or the call as it + *should* behave. A fenced block beats a prose paraphrase: + + ```` + ```rust + parse("a\"b") // => None, want Some("a\"b") + ``` + ```` 3. **Imperative, concise title.** Verb-first, one line, no trailing period — scannable in the list, mirroring commit-message style.