@skyf0xx/hedgehog 4.0.7 → 4.0.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skyf0xx/hedgehog",
3
- "version": "4.0.7",
3
+ "version": "4.0.10",
4
4
  "description": "Install the Hedgehog build discipline (agents + skills) into a repo, for Claude Code, Cursor, or Gemini CLI.",
5
5
  "type": "module",
6
6
  "repository": {
@@ -15,6 +15,7 @@
15
15
  },
16
16
  "scripts": {
17
17
  "check": "node scripts/check.mjs",
18
+ "repro": "node --experimental-sqlite repro/run-all.mjs",
18
19
  "release": "npm version patch -m \"chore: bump version to %s\""
19
20
  },
20
21
  "files": [
@@ -38,6 +38,35 @@ editing those files changes nothing upstream. Ask the user:
38
38
  Do this in a separate directory from the user's own project — never inside
39
39
  it.
40
40
 
41
+ ## Writing the issue or PR
42
+
43
+ Most of Hedgehog's inbound queue is read first by `inbound-triage`, an
44
+ agent, before a human ever sees it. Write for both readers at once, not
45
+ for one at the expense of the other:
46
+
47
+ - Plain technical English. Short sentences, one claim each. No hedging
48
+ ("might possibly", "it seems like"), no filler ("just wanted to
49
+ mention"), no marketing language ("massively improves").
50
+ - Lead with the concrete fact, not the framing. "`hedgehog init` writes
51
+ `.claude/agents/` twice on Windows" beats "I noticed there might be an
52
+ issue with how the installer handles paths."
53
+ - State symptom, expected behavior, and exact repro steps as separate,
54
+ labeled facts — the bug report template's fields exist so a reader
55
+ (human or agent) can find each without parsing prose. Fill every field
56
+ the template asks for; don't collapse them into one paragraph.
57
+ - Cite `file:line` for anything about existing behavior. A claim without
58
+ a citation is a hypothesis, and both readers have to go re-derive it.
59
+ - One issue, one problem. One PR, one change. A bundle forces the reader
60
+ to split it back apart before they can judge any piece of it.
61
+ - Say what you verified, not what you assume. "Ran `node bin/cli.mjs
62
+ init` in a scratch dir, `.claude/skills/` is missing the new
63
+ directory" beats "this probably breaks the install."
64
+
65
+ This is the same register `inbound-triage` uses when it comments back —
66
+ see that skill's "Comment style" section. Writing this way isn't just
67
+ politeness; it's what makes an item triageable in one pass instead of a
68
+ back-and-forth to extract the facts.
69
+
41
70
  ## Workflow
42
71
 
43
72
  1. **Read `CONTRIBUTING.md`** at the Hedgehog repo root before touching