replen 1.0.5 → 1.0.7

package/README.md

@@ -27,7 +27,7 @@ In 60 seconds, the one-liner:
 4. Auto-extracts tags from each (`package.json` deps, `pyproject.toml`, etc.)
 5. Registers them with Replen as your projects (no GitHub PAT needed)
 6. Wires the [@replen/mcp](https://www.npmjs.com/package/@replen/mcp) server into your Claude Code / Codex config
-7. Installs the `/replen-match` skill into `~/.claude/skills/`
+7. Installs the `/replen` skill into `~/.claude/skills/`
 8. Injects a small "Replen integration" section into each project's `CLAUDE.md` + `AGENTS.md`
 
 **What you do not provide:**

package/dist/commands.js

@@ -302,7 +302,7 @@ export async function runCheckNew(argv) {
             const inv = await fetchInventoryStatus(cfg, cwdRepo);
             if (inv && inv.count > 0) {
                 const top = inv.topRepo ? ` Top: ${inv.topRepo}${inv.topSimilarity ? ` (~${inv.topSimilarity}% match)` : ""}.` : "";
-                console.log(`Replen has ${inv.count} candidate${inv.count === 1 ? "" : "s"} queued for ${cwdRepo}.${top} Run /replen-match for full triage.`);
+                console.log(`Replen has ${inv.count} candidate${inv.count === 1 ? "" : "s"} queued for ${cwdRepo}.${top} Run /replen for full triage.`);
             }
         }
         catch {

package/dist/init.js

@@ -160,7 +160,7 @@ export async function runInit() {
     await runFirstIngest({ token: exchange.token, base: exchange.base, savedAt: "" });
     console.log("");
     console.log("  All set. Restart Claude Code and try:");
-    console.log("    /replen-match       → triage today's candidates against this repo,");
+    console.log("    /replen       → triage today's candidates against this repo,");
     console.log("                         in-session, using your subscription tokens");
     console.log("    (no LLM API keys needed — the agent does the reasoning)");
     console.log("");

package/dist/inject-instruction.js

@@ -77,7 +77,7 @@ On your **very first response** of each session:
    shape.
 
 **Additional silent cases** (besides \`(none)\` USER-FACING MESSAGE):
-- The user explicitly typed \`/replen-match\` — redundant.
+- The user explicitly typed \`/replen\` — redundant.
 - The user directly asked for Replen output ("anything from replen
   today?", "what\'s new from replen?"). Just answer.
 
@@ -88,7 +88,7 @@ primitive here.
 
 **Don\'t call \`replen_match\` again on subsequent turns** — once
 per session at start only. The user explicitly types
-\`/replen-match\` if they want a fresh triage mid-session.
+\`/replen\` if they want a fresh triage mid-session.
 `;
 // Find candidate project directories using the same layered discovery
 // as `npx replen sync-projects` — explicit --root flag → REPLEN_PROJECT_ROOTS

package/dist/mcp-setup.js

@@ -4,7 +4,7 @@
 //
 //   - Claude Code  → ~/.claude.json          (JSON, mcpServers object,
 //                                              + SessionStart hook,
-//                                              + /replen-match skill)
+//                                              + /replen skill)
 //   - Codex        → ~/.codex/config.toml    (TOML, [mcp_servers.replen]
 //                                              table; AGENTS.md inject
 //                                              provides session-start

package/dist/skill-install.js

@@ -1,12 +1,12 @@
-// Install the bundled `replen-match` skill into Claude Code's
-// ~/.claude/skills/ tree so users can invoke it via `/replen-match`
+// Install the bundled `replen` skill into Claude Code's
+// ~/.claude/skills/ tree so users can invoke it via `/replen`
 // (or by saying "use replen / triage today / what's new from replen").
 //
 // Idempotent: re-running setup overwrites the skill in place. The
 // skill is the source of truth in Replen's npm package; users
 // shouldn't be hand-editing the installed copy because it'll be
 // clobbered on next `npx replen mcp setup`.
-import { readFileSync, writeFileSync, existsSync, mkdirSync } from "node:fs";
+import { readFileSync, writeFileSync, existsSync, mkdirSync, rmSync } from "node:fs";
 import { homedir } from "node:os";
 import { join, dirname } from "node:path";
 import { fileURLToPath } from "node:url";
@@ -22,10 +22,14 @@ const BUNDLED_SKILLS_ROOT = join(SELF_DIR, "..", "extras", "skills");
 const CLAUDE_SKILLS_ROOT = join(homedir(), ".claude", "skills");
 const SKILLS = [
     {
-        name: "replen-match",
-        files: ["replen-match/SKILL.md"],
+        name: "replen",
+        files: ["replen/SKILL.md"],
     },
 ];
+// Old skill name, removed on setup so the renamed `/replen` is the single
+// source of truth (a stale `/replen-match` copy would otherwise linger and
+// show a duplicate command).
+const LEGACY_SKILL_DIRS = ["replen-match"];
 export function installSkills() {
     if (!existsSync(BUNDLED_SKILLS_ROOT)) {
         // Bundle missing — running from a source tree without the
@@ -36,6 +40,16 @@ export function installSkills() {
         return;
     }
     mkdirSync(CLAUDE_SKILLS_ROOT, { recursive: true });
+    // Migrate: drop the pre-rename /replen-match skill so it doesn't linger.
+    for (const old of LEGACY_SKILL_DIRS) {
+        const oldFile = join(CLAUDE_SKILLS_ROOT, old, "SKILL.md");
+        if (existsSync(oldFile)) {
+            try {
+                rmSync(join(CLAUDE_SKILLS_ROOT, old), { recursive: true, force: true });
+            }
+            catch { /* best effort */ }
+        }
+    }
     let installed = 0;
     for (const skill of SKILLS) {
         for (const rel of skill.files) {

package/extras/skills/{replen-match → replen}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: replen-match
-description: Triage today's Replen candidates against the open codebase, in-session, using subscription tokens. Pulls the day's inventory from Replen, reads the user's local source, produces per-candidate writeups with verdict + effort + concrete file-level impact, then captures star/hide/handoff actions back to Replen. Invoke with `/replen-match` or by saying "run replen on this repo" / "what's new from replen?".
+name: replen
+description: Review Replen's suggestions for the current repo against your code. Replen surfaces libraries, dependency releases, and security advisories relevant to what you're building; this reads the codebase, gives each one a clear verdict and effort estimate with the specific files it affects, and records what you decide. Invoke with `/replen` or by saying "what's new from Replen?".
 ---
 
 # Replen Match — in-session candidate triage
@@ -207,19 +207,36 @@ that actually fit."* If the user agrees, run this checklist:
    what it is · stack · niche/domain · active areas · constraints/non-goals ·
    anti-patterns · integration preferences). Use the project's real domain
    vocabulary, not abstractions.
-3. **Register + tag.** Register the repo: `npx replen sync-projects` (scans the
-   local repos and pushes them to Replen). Then **set the domain tags yourself
-   with the `replen_set_tags` tool** — derive them from the code you just read
-   (e.g. for a Python CCXT market-making engine:
-   `["crypto","trading","market-making","ccxt","quant","backtesting"]`).
-   **Do NOT tell the user to set tags on the web** — that's the sticky step this
-   replaces; set them with the tool. (They can still fine-tune later at
-   app.replen.dev/projects.) Tags matter most right after onboarding, before the
-   project has an embedding — without them a fresh project falls back to
-   language-only matching and surfaces noise.
-4. **Re-run.** Once it has a remote + docs + tags, call `replen_match` again —
-   now it scopes to the project and matches against the real code. (Its embedding
-   lands on the next pipeline run; until then, tags carry the relevance.)
+3. **Register + tag + set capabilities.** Register the repo: `npx replen
+   sync-projects` (scans the local repos and pushes them to Replen). Then, from
+   the code you just read:
+   - **Set domain tags** with `replen_set_tags` — broad domain labels (e.g. for
+     a Python CCXT market-making engine:
+     `["crypto","trading","market-making","ccxt","quant","backtesting"]`).
+   - **Set technical capabilities** with `replen_set_capabilities` — short,
+     GitHub-searchable tech terms for what the project DOES at the tech level
+     (e.g. `["crypto exchange","market data","backtesting","technical
+     analysis"]`; for a defense CV pipeline `["computer vision","object
+     detection","satellite imagery","geospatial mapping"]`). Derive these from
+     the actual imports/deps, not guesses. This is the highest-leverage step:
+     the server builds the project's facet vectors from these IMMEDIATELY (no
+     waiting for a scheduled run), and they drive both faceted matching and the
+     shared capability catalogue.
+
+   **Do NOT tell the user to set tags/capabilities on the web** — that's the
+   sticky step this replaces; set them with the tools. (They can fine-tune later
+   at app.replen.dev/projects.) These matter most right after onboarding — they
+   give a fresh project working query vectors before any server-side inference.
+4. **Embed it now (don't wait for the daily run).** A freshly-registered
+   project has no embedding yet, so matching falls back to language/tags only
+   (noise) until the next scheduled run. Trigger an immediate run with the
+   `replen_run` tool — it builds the project's summary + embedding + initial
+   candidates from the README/CLAUDE.md you just pushed. It's async: poll
+   `replen_status` until the phase reports inventory ready (~1–3 min). Tell the
+   user it's processing.
+5. **Re-run.** Once the run finishes, call `replen_match` again — now scoped
+   AND embedded, matching against the real code (a dev-tool that only shared the
+   project's language now scores low on cosine and gets floored out).
 
 Note on recording actions: always use the MCP tools — `replen_state` (star /
 hide / handoff), `replen_record_triage` (your verdict), `replen_set_tags` — for

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replen",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "description": "Make your AI coding tools smarter. One command, no API keys. Replen scouts the OSS firehose against your projects and surfaces drop-in libraries, ideas to port, and dead deps to swap — the match decision happens inside your AI tool's session on your subscription tokens. 1-3 actionable matches a month, by design.",
   "type": "module",
   "bin": {