navori 0.7.8 → 0.8.0

package/dist/assets/core/core-assets/agents/commit-pr-pilot.md

@@ -142,7 +142,7 @@ Never open the PR with the gate red.
 3. Draft a Conventional commit message:
    - Type: `feat | fix | docs | refactor | perf | test | chore | style | build | ci | revert`.
    - Scope: lowercase, derived from the touched area (module/domain).
-   - Description: imperative, ≤70 chars, no trailing period, language defined by the config's `commits`.
+   - Description: imperative, ≤70 chars, no trailing period, language defined by `{{commits}}`.
    - Optional body with the WHY if the decision isn't obvious.
 4. If you touch potentially sensitive files (`.env*`, credentials, odd lockfiles), **flag the user before staging**.
 5. `git add <files>` (prefer explicit over `git add -A`).
@@ -235,7 +235,7 @@ Never open the PR with the gate red.
 **`Closes` is syntax, not prose.** GitHub links and auto-closes an issue only
 when the body carries `Closes` / `Fixes` / `Resolves` followed by `#<N>`, **in
 English**, pointing at an issue of this same repo. The rest of the body follows
-the config's `commits` language and this keyword does NOT: translated (`Cierra
+the `{{commits}}` language and this keyword does NOT: translated (`Cierra
 #<N>`) it is an ordinary sentence, GitHub links nothing, the issue stays open
 and no error says so. That silence is the whole defect — navori's own repo
 shipped 8 PRs that way and closed all 8 issues by hand before anyone noticed
@@ -266,7 +266,7 @@ wc -c CLAUDE.md                                  # after
 - ❌ Never skip hooks (`--no-verify`) unless the user explicitly asks.
 - ❌ Never ask for a merge / approve the PR yourself. Your job ends with the URL.
 - ❌ Never `gh pr checks --watch`: it takes no timeout and would hang the turn before the URL reaches the user.
-- ✅ Commit and PR message in the language defined by the config's `commits` (`conventional-es` = Spanish MX, `conventional` = English) — except the `Closes #<N>` keyword, which GitHub parses and which stays in English in any language (see the body template).
+- ✅ Commit and PR message in the language defined by `{{commits}}` (`conventional-es` = Spanish MX, `conventional` = English) — except the `Closes #<N>` keyword, which GitHub parses and which stays in English in any language (see the body template).
 - ✅ If you introduce a new pattern or non-obvious decision that wasn't already in `impl_<feature>.md`, leave a note in the PR body ("Decisions" section).
 
 ## Anti-patterns

package/dist/assets/core/core-assets/agents/implementer.md

@@ -100,7 +100,7 @@ Write `.claude/progress/impl_<feature>.md`:
 - ...
 
 ## Suggested commit
-`feat(<scope>): ...` (Conventional, atomic, language per the config's `commits`)
+`feat(<scope>): ...` (Conventional, atomic, language per `{{commits}}`)
 ```
 
 ## Communication with the leader

package/dist/assets/core/core-assets/managed/cierre-sesion.md

@@ -6,7 +6,7 @@ Before closing the session:
 2. **History**: add an entry in `progress/history.md` with `## YYYY-MM-DD HH:MM <agent> — <summary>` + changes + gate status. **One redaction, every destination**: write that summary once and reuse the same text wherever else this closeout persists it (a memory store, for instance) — never write the same session up twice. If the session turned up a durable fact that outlives this repo (a data model, a business rule, a cross-service contract, a shared gotcha), promote it with the `dominio` skill instead of leaving it only in session memory.
 3. **Clear current**: leave `progress/current.md` at `idle` or with the explicit next step.
 4. **No temporaries**: delete scratch files; don't leave `console.log`, `debugger`, or commented-out code.
-5. **Conventional commit**: `feat|fix|chore|docs(scope): message`, atomic, in the language defined by the config's `commits`.
+5. **Conventional commit**: `feat|fix|chore|docs(scope): message`, atomic, in the language defined by `{{commits}}`.
 6. **Park on base**: once the cycle's work is committed and its branch pushed (PR opened when the flow calls for one), leave the repo standing on the base branch, synced: `git switch {{branchBase}}` then `git pull --ff-only`. The point is where the NEXT session starts from — a repo parked on last week's feature branch breeds branches cut from stale bases. Rules that make it safe:
    - **Never delete the feature branch.** This is position hygiene, not history hygiene; the branch stays for its pending merge and for `babysit-prs`.
    - Only with a **clean working tree** and the cycle's commits pushed. Anything unpushed or uncommitted → do NOT switch; say what was left and leave parking to the user.

package/dist/assets/core/core-assets/skills/pr-create.md

@@ -9,7 +9,7 @@ type: reference
 The commit + PR flow has **one owner**: the `commit-pr-pilot` agent
 (`.claude/agents/commit-pr-pilot.md`). It owns the pre-flight, the PR gate
 (`{{qualityGate.full}}` green), the review/R1 handling, the body template and the
-commit/PR language (per the config's `commits`).
+commit/PR language (per `{{commits}}`).
 
 **To close a cycle, invoke `commit-pr-pilot`.** Don't draft the PR from a separate
 template here — a second flow drifts from the pilot (that's why this skill was

package/dist/assets/core/package.json

@@ -10,6 +10,6 @@
     "core-assets"
   ],
   "engines": {
-    "node": ">=20"
+    "node": ">=22"
   }
 }

package/dist/assets/plugins/codegraph/plugin.json

@@ -2,7 +2,7 @@
   "id": "codegraph",
   "name": "CodeGraph \u2014 surgical code context",
   "description": "Pre-built AST code graph via MCP: symbols, call paths and blast-radius in one call, fewer grep/read loops",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "managed": [
     {
       "id": "codegraph-protocol",
@@ -24,7 +24,8 @@
     "args": [
       "serve",
       "--mcp"
-    ]
+    ],
+    "alwaysLoad": true
   },
   "settingsFragment": {
     "permissions": {

package/dist/assets/plugins/jscpd/plugin.json

@@ -2,14 +2,8 @@
   "id": "jscpd",
   "name": "jscpd (code duplication detector)",
   "description": "Detección de duplicación de código en el diff vs branch base",
-  "version": "0.0.4",
-  "managed": [
-    {
-      "id": "jscpd-protocol",
-      "file": "managed/jscpd-protocol.md",
-      "recommendedAgent": "reviewer"
-    }
-  ],
+  "version": "0.0.5",
+  "managed": [],
   "externalTool": {
     "name": "jscpd",
     "checkBinary": "jscpd",
@@ -35,5 +29,16 @@
       "statusMessage": "navori/jscpd: dup check"
     }
   ],
-  "invariants": ["jscpd", "do not approve"]
+  "invariants": [
+    "jscpd",
+    "do not approve"
+  ],
+  "skills": [
+    {
+      "id": "jscpd-review-extension",
+      "file": "skills/jscpd-review.md",
+      "recommendedAgent": "reviewer",
+      "injectInto": ".claude/skills/review-diff/SKILL.md"
+    }
+  ]
 }

package/dist/assets/plugins/jscpd/skills/jscpd-review.md

@@ -0,0 +1,19 @@
+---
+name: jscpd-duplication-gate
+description: Use when reviewing a diff and the repo renders the jscpd plugin — scan the changed files for duplication before approving, and treat clones over the threshold as a blocker.
+type: behavior
+---
+
+## Code duplication (jscpd)
+
+Before approving a change, run jscpd over the diff vs the base branch.
+
+- Only over modified files:
+  ```
+  git diff --name-only {{branchBase}}...HEAD | grep -E '\.(ts|tsx|js|jsx)$' | xargs jscpd --silent
+  ```
+- If it reports clones >0 with the project's threshold: **do not approve** the change without justification (reviewers must ask for a refactor or extraction).
+- Silent skip if `jscpd` is not in `PATH` (don't block if the dev doesn't have the tool installed).
+
+The commit gate runs this for you (`PreToolUse` on `git commit`), so this text is
+the reasoning and the manual command — not the mechanism.

package/dist/assets/plugins/semgrep/plugin.json

@@ -2,14 +2,8 @@
   "id": "semgrep",
   "name": "semgrep (security + pattern analysis)",
   "description": "Detección de vulnerabilidades y patrones inseguros local opt-in",
-  "version": "0.0.4",
-  "managed": [
-    {
-      "id": "semgrep-protocol",
-      "file": "managed/semgrep-protocol.md",
-      "recommendedAgent": "reviewer"
-    }
-  ],
+  "version": "0.0.5",
+  "managed": [],
   "externalTool": {
     "name": "semgrep",
     "checkBinary": "semgrep",
@@ -34,5 +28,15 @@
       "statusMessage": "navori/semgrep: security scan"
     }
   ],
-  "invariants": ["run semgrep over the diff"]
+  "invariants": [
+    "run semgrep over the diff"
+  ],
+  "skills": [
+    {
+      "id": "semgrep-review-extension",
+      "file": "skills/semgrep-review.md",
+      "recommendedAgent": "reviewer",
+      "injectInto": ".claude/skills/security-guidance/SKILL.md"
+    }
+  ]
 }

package/dist/assets/plugins/semgrep/skills/semgrep-review.md

@@ -0,0 +1,24 @@
+---
+name: semgrep-security-gate
+description: Use when auditing security or closing a change that touches auth, RBAC, secrets or input validation and the repo renders the semgrep plugin — run the static scan over the diff before closing.
+type: behavior
+---
+
+## Local security gate (semgrep)
+
+Before closing a relevant change (auth, RBAC, secrets, input validation), run semgrep over the diff.
+
+- Quick diff scan:
+  ```
+  git diff --name-only {{branchBase}}...HEAD | xargs semgrep scan --config=p/default --error --metrics=off
+  ```
+- Full project scan (slower, opt-in):
+  ```
+  semgrep scan --config=p/default --error --metrics=off
+  ```
+- `p/default` (not `auto`) on purpose: deterministic and telemetry-off — mirrors the plugin's check script.
+- Custom rules: see `.semgrep.yml` at the repo root if it exists.
+- Silent skip if `semgrep` is not installed (don't block if the dev doesn't have it).
+
+The commit/push gate runs this for you (`PreToolUse`), so this text is the
+reasoning and the manual command — not the mechanism.

package/dist/assets/plugins/tgrep/managed/tgrep-protocol.md

@@ -12,6 +12,8 @@ It carries an `allow` rule, so it runs with no permission prompt in every mode a
 
 That decision lives in the script rather than in this text on purpose: `SessionStart` hooks don't run for subagents, so a subagent cannot know what the machine has — but the same command is right for all of them.
 
+**Searching is not extracting.** The index answers *which file holds X*. Once you already know the file and want its lines, `grep -n "x" that-file` or `Read` is the right call and the cheaper one — the wrapper would reindex the whole tree to read a single file. Measured on real sessions, this is a third of the shell `grep` calls, and all of them are correct.
+
 ### Routing: the graph or the wrapper
 
 | The question | First call |