@skyf0xx/hedgehog 0.1.9 → 0.1.11

package/bin/cli.mjs

@@ -25,6 +25,13 @@ const yellow = (s) => paint('33', s);
 const red = (s) => paint('31', s);
 const dim = (s) => paint('2', s);
 
+// npm's publish step silently drops any file literally named `.gitignore`
+// (also `.npmignore`, `.git`, etc.) from the tarball, even when the
+// containing directory is listed in `files` — there's no way to opt back
+// in via `files` or `.npmignore`. So golden-core's is stored under this
+// name and renamed back to `.gitignore` on copy, per dir entry below.
+const DOTFILE_RENAMES = { 'gitignore.template': '.gitignore' };
+
 // ── the payload: what gets copied, and to where under the target repo ───
 // `dir` entries copy a whole tree; `file` entries copy a single file and
 // may rename (templates lose their src/templates/ prefix at the root).
@@ -61,7 +68,8 @@ async function plannedFiles(entry) {
     if (st.isDirectory()) {
       for (const name of await readdir(abs)) await walk(join(rel, name));
     } else {
-      out.push({ src: abs, dest: join(DEST_ROOT, entry.to, rel) });
+      const renamed = DOTFILE_RENAMES[rel] ?? rel;
+      out.push({ src: abs, dest: join(DEST_ROOT, entry.to, renamed) });
     }
   }
   await walk('.');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog",
-  "version": "0.1.9",
+  "version": "0.1.11",
   "description": "Install the Hedgehog build discipline (agents + skills) into a repo.",
   "type": "module",
   "repository": {

package/src/golden-core/gitignore.template

@@ -0,0 +1,20 @@
+node_modules
+dist
+tmp
+out-tsc
+.env
+.env.local
+*.log
+.DS_Store
+
+.nx/cache
+.nx/workspace-data
+.nx/polygraph
+.claude/worktrees
+.claude/settings.local.json
+vitest.config.*.timestamp*
+
+# Next.js
+.next
+out
+test-output

package/src/templates/CLAUDE.md

@@ -20,6 +20,16 @@ This project is built with **Hedgehog**: a backend-first, one-step-at-a-time
 build discipline. The rules below aren't project preferences — they're how
 the build stays mechanically correct. Follow them exactly.
 
+## First message in a fresh install
+
+If `{{PROJECT_SUMMARY}}` above is still an unfilled placeholder, this is a
+brand-new install and nothing has been built yet. Open with something
+short and warm — 🦔 plus one line asking what the user wants to build —
+then hand straight to `planner` to run Intake. Don't re-explain the
+discipline or summarize this file; the greeting is one line, not a tour.
+Skip this entirely once the placeholder is filled in — every later session
+starts with `TODO.md`, not a greeting.
+
 ## How to work here
 
 The build is a loop of small, gated, committed steps. You never hold the