Knowledge Forge

Plugin forge from marketplace knowledge-forge in mimir45/Knowledge-Forge. Commands read from the repo's manifest — 1 month ago.

Skills (6)

• forge-check

  Use when the user asks to run the weekly vault health check — "run forge check", "what needs attention in the vault", "give me the weekly rollup", "any drift/duplicates/orphans to look at", or on a scheduled/cron-style invocation of the weekly job. Not for a single explanatory question (that's `forg

• forge-dataset-stats

  Use when the user asks what training data the vault has accumulated — "how much training data do I have", "can I fine-tune on this yet", "show dataset stats", "what's in d1/d3", "is there enough for a LoRA". Not for whether the vault is paying off day to day (that's `forge-stats`, which reads the te

• forge-export-dataset

  Use when the user wants to get their captured training data out — "export the dataset", "give me the d3 pairs", "export for fine-tuning", "dump the routing data as CSV", "anonymize and export". Not for asking how much data there is (that's `forge-dataset-stats`, which writes nothing) and not for scr

• forge-init

  Use when the user wants to set up Knowledge Forge for a vault they have not configured yet — "set up forge", "install knowledge forge here", "onboard this vault", "run forge init", or the first time `forge recall`/`forge check` fails because no config exists. Not for changing an existing config (edi

• forge-stats

  Use when the user asks whether Knowledge Forge is paying off — "is the vault helping", "what am I asking about most", "show forge stats", "what gaps are there", "how's the hit rate", "am I saving time with this". Not for a single explanatory question (that's `forge`), not for the weekly health rollu

• forge

  Use when the user asks an explanatory question about a technology, concept, or integration — "how does X work", "what is X", "explain X", "how do I integrate X with Y", "what's the difference between X and Y", "best practices for X", "why does X do Y". Checks the vault before researching, then answe

Subagents (4)

• forge-codebase-scout

  Finds how a topic is actually used in the current repo — file:line examples, local conventions, project-specific config — as the differentiator between a generic note and one grounded in this codebase. Read-only, no Bash.

• forge-librarian

  Merges/links a gated note into the vault, populates code_refs, rebuilds the index, and commits with the Forge-Write trailer. Runs only after forge gate has already passed a draft — never a gate bypass.

• forge-researcher

  Answers N research questions about an external topic (a library, protocol, pattern) from authoritative web sources, returning findings with dated citations. Read-only — never writes to the vault or the repo.

• forge-verifier

  Spot-checks a draft's claims and code snippets — compiles snippets via forge verify-code, cross-checks version-specific claims against sources — and returns pass/fail per claim plus a confidence assignment. Never runs a compiler by hand.

Hooks (4)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}"/hooks/session-context

• UserPromptSubmit

  "${CLAUDE_PLUGIN_ROOT}"/hooks/user-prompt-intent

• SessionEnd

  "${CLAUDE_PLUGIN_ROOT}"/hooks/session-end-capture

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/hooks/post-tool-cache-source

Similar plugins