Have you already built this? Check your own repos first.
vibe-recall indexes the repos you've already written and answers one question while you spec the next feature: have I built something like this? It ranks shallow cards against your phrase or spec file, then re-reads the winning hit live at its current HEAD before it says anything about the source. A stale card can point. Only a live read can claim.
Includes6 commands · 9 skills
Six commands, from index to verified brief.
Index the estate, sweep it for prior art, then verify one hit live. It never writes code and never edits anything inside a repo it indexes.
Map the estate.
Walks your configured estate root and builds or refreshes a shallow card per in-scope repo. Duplicate clones collapse to one canonical card, and diverged pairs get named for you to resolve instead of picked silently.
Reach for it on first run, and whenever your repos have moved since the last index.
Rank prior art against a phrase or spec.
Takes a phrase or a spec file path, checks the current repo's own source first, then ranks indexed cards. Scoring is deterministic and explains itself. Forks and vendored checkouts are excluded by default, and zero hits comes back as a real answer.
Reach for it before you write the spec for something that feels familiar.
Verify one hit at current HEAD.
Re-reads the named repo live and writes up what is actually there. It is the only skill allowed to author a claim about source. Ends with a handoff to vibe-taker, which does the moving.
Reach for it when a sweep hit looks real and you're about to lean on it.
Promote a card from shallow to deep.
Reads a repo's actual source and records its real features on the card. With no argument it takes the top of the demand-ranked queue: non-deep cards ordered by recall hits, then last-commit recency.
Reach for it when the same repo keeps surfacing and its card is still thin.
Check index coverage and hygiene.
Reports repos indexed, deep cards, queue depth, diverged pairs, foreign repos by name, scan-truncated counts, and secret-file skips. Also flags a missing runtime dependency with the fix.
Reach for it when a sweep feels thin and you want to know why.
State-aware router.
Reads your config and index state and recommends one next command. It never fires index or anything mutating on its own.
Reach for it when you're not sure what to run next.
The index suggests. Only a live read claims.
A card holds shapes, never content: symbol names, dependency names, entrypoint paths, and short claim strings pulled from README and CLAUDE.md. No file bodies. Files that are .env-shaped by name, or that trip a secret-shape scan by content, are skipped. The index is a map of your estate, not a mirror of it.
Because a card is a snapshot from whenever index last ran, it is good enough to rank and point, never good enough to quote. /vibe-recall:brief opens the file again in the current session, at the repo's current HEAD, before it writes a word about the source. The fork filter reads authorship from git history and fails open: a repo it can't classify is never treated as foreign.
Walls are refusals. You set tenant walls in first-run setup, nothing ships pre-seeded, and a path under a wall is never indexed, ranked, or named in the index. There is no override flag. A UserPromptSubmit hook can surface a banner when your prompt reads like you're about to build something. Cards and config live in the plugin's local data home, never inside an indexed repo, and there is no cross-machine sync.
Two channels.
Stable marketplace
Tagged releases, promoted via the Vibe Plugins marketplace.
/plugin marketplace add estevanhernandez-stack-ed/vibe-plugins /plugin install vibe-recall@vibe-plugins
Canary bleeding edge
Latest main from this repo.
/plugin marketplace add estevanhernandez-stack-ed/Vibe-Recall /plugin install vibe-recall@vibe-recall
First use runs setup: estate root, tenant walls, optional GitHub accounts for remote-only listing. Needs Node; one runtime dependency (ajv) installs with the plugin, and vitals tells you if it didn't. Indexes only your own estate root, no public code search.
One plugin in a family.
Vibe Plugins are a coordinated family — installed independently, composed when present.
