@skyf0xx/hedgehog 5.1.7 → 5.1.8

package/README.md

@@ -1,4 +1,5 @@
-# Turn AI from a code generator into a reliable software engineer ⭐
+# H E D G E H O G
+![Incredible Software Engineer](https://raw.githubusercontent.com/skyf0xx/hedgehog/master/docs/images/incredible.png)
 
 [![Total downloads](https://raw.githubusercontent.com/skyf0xx/hedgehog/master/badges/npm-downloads.svg)](https://www.npmjs.com/package/@skyf0xx/hedgehog)
 [![Support Hedgehog](https://raw.githubusercontent.com/skyf0xx/hedgehog/master/badges/kofi-top.svg)](https://ko-fi.com/skyf0xx)
@@ -138,16 +139,25 @@ Sequence
 Artifact
 ```
 
-### Anything else
+### Web Apps/ PWAs
 
-A CLI, a library, a browser extension, a data pipeline, etc. fitting neither shape gets its own build order, designed at intake rather than chosen from a menu — starting from a battle-tested blueprint (in [`hedgehog-core-authored`](https://github.com/skyf0xx/hedgehog-core-authored)'s `hedgehog-core-design` skill) for the system's shape where one exists.
+Local-first simple mobile compatible web  apps: trackers, journals, planners, etc:
 
-Run `init` with no core flag: planning intake names the system shape, picks
-the stack, derives the layers, and locks them to `.hedgehog/core.yaml`,
-then generates that workspace and builds it one verified layer at a time.
+``` text
+Schema
+  ↓
+Repository
+  ↓
+Hook
+  ↓
+Screen
+```
 
-The enforcement remains the same: ordered steps,
-scoped file access and a verification command per layer.
+### Anything else
+
+A CLI, a library, a browser extension, a data pipeline, etc. gets its build order.
+
+Where possible, Hedgehog uses a battle-tested blueprint in [`hedgehog-core-authored`](https://github.com/skyf0xx/hedgehog-core-authored/tree/main/skills/hedgehog-core-design/blueprints) for the system's shape where one exists.
 
 ### Existing codebases
 
@@ -216,35 +226,21 @@ Hedgehog improves the **system AI builds inside**.
 
 Hedgehog uses a fixed stack and build order for each core. The tooling enforces architectural boundaries so correctness does not depend on the AI remembering instructions.
 
-See [ARCHITECTURE.md](ARCHITECTURE.md) for the full design.
-
-## Authoring a new core
-
-A core is an npm package carrying a pre-built, pre-verified workspace plus the agents and skills that build it. The package contract, at the package root:
-
-- `hedgehog-core.yaml` — the manifest naming the core (matching its registry entry), its language, and where each contributed piece lives in the package: `workspace/` (the scaffold, omitted by a core that scaffolds nothing), `CLAUDE.core.md` (fills the installed `CLAUDE.md` shell's core section), `agents/<name>.md`, `skills/<name>/`, and any `vendor_skills/<name>/`. Its `engine` key states the engine line the core's agents and skills are written against, as a caret range over a three-part version (`engine: "^5.0.0"`); an older CLI refuses the core rather than landing a payload it cannot drive.
-- `core.yaml` — the layer sequence and per-layer verify commands, in the same shape `src/db/core.mjs` loads for an authored core.
-
-Adding the package to the CLI's `init` menu is one entry in `src/registry/cores.json`: the package name, the version range to resolve, an install flag, and the `selects_when` prose. That entry owns the selection prose — `planner` reads it in Phase 0, before any core package is fetched — so the manifest leaves it out; a `selects_when` in a manifest is never read.
+See [ARCHITECTURE.md](ARCHITECTURE.md) for the full design, and
+[AUTHORING-CORES.md](AUTHORING-CORES.md) for how to build and register a
+new one.
 
 ## Credits
 
-Hedgehog uses [BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD)
-(`bmad-code-org/BMAD-METHOD`) for planning, MIT-licensed.
+- Planning runs on [BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD). 
 
-The `nx-generate`, `nx-run-tasks`, `nx-workspace`, and
-`link-workspace-packages` skills are adapted from
-[nx-ai-agents-config](https://github.com/nrwl/nx-ai-agents-config)
-(`nrwl/nx-ai-agents-config`), MIT-licensed, rewritten for Hedgehog's
-pnpm-only workspace convention.
+- Nx skills adapted from [nx-ai-agents-config](https://github.com/nrwl/nx-ai-agents-config).
 
-`front-end-eng`'s animation skills (`vendor-skills/GSAP/`) are vendored from
-[gsap-skills](https://github.com/greensock/gsap-skills)
-(`greensock/gsap-skills`), MIT-licensed.
+- Animation skills vendored from [gsap-skills](https://github.com/greensock/gsap-skills).
 
 ## Support Hedgehog
 
-If Hedgehog helps you build better software with AI, **give it a ⭐ on GitHub**, or [buy me a coffee on Ko-fi](https://ko-fi.com/skyf0xx).
+If Hedgehog helps you build better software with AI, **give it a ⭐ on GitHub**.
 
 [![GitHub stars](https://raw.githubusercontent.com/skyf0xx/hedgehog/master/badges/github-stars.svg)](https://github.com/skyf0xx/hedgehog/stargazers)
 [![Total downloads](https://raw.githubusercontent.com/skyf0xx/hedgehog/master/badges/npm-downloads.svg)](https://www.npmjs.com/package/@skyf0xx/hedgehog)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog",
-  "version": "5.1.7",
+  "version": "5.1.8",
   "description": "Install the Hedgehog build discipline (agents + skills) into a repo, for Claude Code, Cursor, or Gemini CLI.",
   "type": "module",
   "repository": {

package/src/skills/conventional-commits/SKILL.md

@@ -44,8 +44,8 @@ Run in parallel:
 - `git log -10 --oneline` to confirm the project's existing commit style
 - Run `hedgehog status` for which steps/modules are in flight
 
-Read every changed file's diff fully. You cannot group changes you
-haven't read.
+Read every changed file's diff fully before grouping — you cannot group
+changes you haven't read.
 
 ### 2. Group hunks into logical commits
 
@@ -72,8 +72,7 @@ Do NOT group:
 
 1. **Build-sequence order.** Schema before contract, contract before
    repository, repository before service, service before controller —
-   same dependency order the Loop builds in, even reconstructing after
-   the fact.
+   the same dependency order the Loop builds in.
 2. **Upstream fix before its fast-forwarded dependents**, for a
    Correction Protocol cleanup — the fix commit needs to make sense
    before the commits that changed because of it.
@@ -102,9 +101,8 @@ Then execute each commit:
 - Verify clean state with `git status` before the next commit.
 
 If a pre-commit hook (lefthook: typecheck/lint/test) fails: fix the
-issue, re-stage, create a NEW commit. Never `--amend` after a hook
-failure — a commit that fails the gate did not happen, so amending would
-rewrite the wrong thing.
+issue, re-stage, create a NEW commit — a commit that fails the gate did
+not happen, so amending would rewrite the wrong thing (see Hard rules).
 
 ### 5. Commit format