lore

Plugin lore from marketplace trailhead-local in trailhead-ai/trailhead. Commands read from the repo's manifest — 2 days ago.

Skills (6)

• correct

  Correct a record — decide whether the fix is applied now or tracked, and for a frozen record whether it is an in-place amend or a supersession, then do it. Use when the operator says a record is wrong or out of date, or asks to fix, correct, change, update or revise an ADR, a spec, a decision, or a

• flush

  Evaluate outstanding session candidates into vault records, then flip the session clean. Runnable at any time — not just at session end. Clean session → nothing to flush. Dirty session → read the candidate log, apply agent judgment to evaluate each outstanding candidate (those after the flushed-at w

• record

  Capture ONE specific item now — a single deliberate capture you already have in mind. Orients you to the two capture surfaces and helps you pick: a `lore session candidate` (the default, for findings that arise during work — promoted to a durable record at flush) versus a direct `lore record` write

• research

  Dispatch a lore research agent — the deep `investigator` for open-ended how/why/tradeoff investigations that span multiple files and systems, or the lighter `researcher` for quick lookups and polling `blocked`-status tasks. Use for /lore:research, "investigate how X works", "research the tradeoffs o

• search

  Read the lore vault — run a KQL-subset query against the global lore index and return matching records. This is the READ/lookup path; it never writes. Use for /lore:search, "search the vault", "look up what we know about X", "find records where kind:Y and area:Z", "recall prior context on …".

• sync

  Commit, pull, and push the lore vaults. Use for /lore:sync, "commit the vault", "sync the vault", "push the vault", "pull the vault".

Subagents (3)

• investigator

  Deep-investigation specialist for the lore vault AND source code — open-ended "how does X work", "why was Y built this way", or "what are the tradeoffs of Z" questions that span vault notes (areas, decisions, lessons, tasks, sessions, specs) and the code they describe. Use when you need thorough cro

• librarian

  Searches and synthesizes across the lore vault — area profiles, decisions, lessons, tasks, collaborations, sessions, and specs. Understands the taxonomy and returns synthesized answers with [[wikilinks]] to source records, not raw dumps. Works entirely through the `lore` CLI (`lore search` + `lore r

• researcher

  Lighter lookups across the lore vault and the codebase — locates a specific note, API, library, function, config option, or concept and returns a pointer (path:line or URL) plus the minimum relevant excerpt. Runs on Haiku with low effort, so it's the cheap path when you don't need the `investigator`