From ohara
Use the ohara MCP (find_pattern + explain_change) to answer "how did we do X before?" or "why does this code look this way?" against this repo's git history. Trigger on lineage / prior-art / git-archaeology questions; skip for current-state grep, fresh repos with no history, or general programming questions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ohara:lineageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This repository has been indexed by [ohara](https://github.com/vss96/ohara), a
This repository has been indexed by ohara, a
local-first git-history lineage engine. Two MCP tools are available on the
ohara server.
find_pattern whenexplain_change when(file, start, end) rangeGrep / Read insteadBoth tools return a _meta.compatibility field describing the index state:
compatible — proceed normallyquery_compatible_needs_refresh — queries still work; suggest
ohara index --force for completenessneeds_rebuild — find_pattern will refuse with a structured error.
Surface the rebuild command (ohara index --rebuild --yes) to the user.
Do not silently retry.unknown — pre-v0.7 index without metadata; suggest ohara index --forceFor index lifecycle questions (when to run, --force vs --rebuild, etc.) see
the ohara:indexing skill.
combined_score values negative → low confidence. Treat as
"no strong prior art" rather than acting on the top hit.provenance: "INFERRED" is normal for find_pattern (semantic match);
explain_change returns "EXACT" because git blame is git-truth.recency_weight near 1.0 means the hit is recent; near 0.0 means old.
The cross-encoder rerank already factors this in — don't double-discount.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub vss96/ohara --plugin ohara