@cogit/cli 0.24.0 → 0.25.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cogit/cli",
-  "version": "0.24.0",
+  "version": "0.25.0",
   "description": "Git remembers what changed. cogit remembers why.",
   "license": "MIT",
   "keywords": [
@@ -45,6 +45,7 @@
   "devDependencies": {
     "@inquirer/prompts": "^8.7.4",
     "commander": "^15.0.0",
+    "mermaid": "^11.17.2",
     "tsup": "^9.0.0",
     "zod": "^4.6.7"
   }

package/skills/record/SKILL.md

@@ -78,6 +78,27 @@ Every message grows from an earlier one; a thread that starts something new is a
 - Hints, not rules: `gapMinutes`, `resumed`, `commitBetween` (a real commit landed in this
   repo between them), `lastMessages`, and for a first message `candidates`/`continuesHint`.
 
+## Shape
+
+A message that landed commits gets a `shape`: a small representation of what the change does,
+between its Intent (the decision and reason above) and its Code (the diff). Add it on that
+message's node, with the node's commit hashes:
+
+```json
+"shape": { "tools": [{ "kind": "pseudo", "text": "1. ...\n2. ..." }], "commits": ["abc1234"] }
+```
+
+Two tools:
+
+- `pseudo`: numbered plain-language steps of the new logic, naming the functions and files.
+- `mermaid`: a Mermaid `flowchart TD` (or `LR`) of the new path between files or functions,
+  at most 15 nodes. Quote labels that hold spaces or punctuation.
+
+Pick one, both, or none (`{ "tools": [] }` means nothing worth showing). Skip messages whose
+commits are only release/version bumps, lockfiles or CHANGELOG, or change fewer than 5 lines
+in total. Write it in the conversation's language; the CLI validates each output and keeps an
+invalid diagram as text.
+
 ## Branch summary
 
 A branch starts at a root or where a message gets a second child. Its first message carries a