Run any Skill in Manus with one click

repolore

Stars4

Forks0

UpdatedJune 30, 2026 at 07:02

Give any repository a code-derived LLM wiki — cited claims, blob-SHA drift checking, coverage auditing, a generated index. Use when the user wants to set up, health-check, or refresh a maintained wiki / knowledge base / "lore" distilled from the codebase, or asks why-is-it-like-this documentation that stays honest as code changes.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

emyann

emyann/repolore

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	repolore
description	Give any repository a code-derived LLM wiki — cited claims, blob-SHA drift checking, coverage auditing, a generated index. Use when the user wants to set up, health-check, or refresh a maintained wiki / knowledge base / "lore" distilled from the codebase, or asks why-is-it-like-this documentation that stays honest as code changes.
license	MIT

repolore

Your codebase has lore — the decisions, gotchas, and why-things-are-the-way-they-are that live in nobody's head for long. This skill makes you write it down, cite it, and keep it honest: an in-repo, human-editable wiki distilled from the code, with per-claim citations and mechanical (blob-SHA) staleness detection. The code is always the source of truth; the wiki is the orientation layer.

<SKILL_ROOT> below means the directory containing this SKILL.md (it ships with scripts/, templates/, and references/ alongside).

Six workflows — pick by what the user asked

User intent	Procedure to read and execute
"set up a wiki / knowledge base for this repo" (once per repo)	`<SKILL_ROOT>/references/init.md`
"is the wiki up to date?" / before relying on wiki content	`<SKILL_ROOT>/references/check.md`
"update the wiki" / check reported stale pages	`<SKILL_ROOT>/references/refresh.md`
"audit the wiki for wrongness" / check's dust line reports overdue pages / "triage the findings"	`<SKILL_ROOT>/references/audit.md`
"update repolore's tooling in this repo" / check reported newer tooling	`<SKILL_ROOT>/references/update.md`
"activate repolore extras" (hook, team-wide nudge, auto-update) / after an update adds capabilities	`<SKILL_ROOT>/references/setup.md`

Read the matching procedure fully and follow it exactly, substituting <SKILL_ROOT> as defined above. Each is self-contained; the scripts they invoke are stdlib-only (node + git, no npm install).

Day-to-day, outside those workflows: once a repo is initialized, its wiki rules live in <wikiRoot>/AGENTS.md inside that repo (location recorded in .repolore/manifest.json) — pages are drafted on demand ("draft features/<slug> from the wiki plan") and updated as part of the change that altered the behaviour they describe.

Also available as a Claude Code plugin (/plugin marketplace add emyann/repolore), where these workflows surface as the namespaced commands /repolore:init, /repolore:check, /repolore:refresh.

More from this repository

same repository

audit

emyann/repolore

Audit the wiki for wrongness behind unchanged bytes — per-claim verification of fresh pages against the code (the drift class hashes can't see), findings-inbox triage, and a reviewable commit. Use when the user asks to audit/verify the wiki's truthfulness, when check's dust line reports never-audited or overdue pages, or to triage FINDINGS.md.

2026-06-134

check

emyann/repolore

Report the health of the repo's LLM wiki — stale or unmanaged pages, new code with no page, index drift, page budget, tooling updates. Use when the user asks whether the wiki is up to date, before relying on wiki content for a task, or after merging significant changes.

2026-06-114

setup

emyann/repolore

Detect and activate optional repolore capabilities that need consent — the post-commit wiki nudge (per-machine or team-wide), team auto-update via project settings. Presents available-but-inactive items as one simple question. Use when the user asks to set up, activate, or enable repolore extras, or after an update adds new capability scripts.

2026-06-114

update

emyann/repolore

Update the repo's vendored repolore tooling (.repolore/scripts, wiki AGENTS.md, templates) to the installed version — safe regeneration that never overwrites local edits without consent. Use when wiki-check reports newer tooling, after updating the repolore plugin, or when the user asks to update repolore in this repo.

2026-06-114

init

emyann/repolore

Bootstrap an LLM-maintained, code-derived wiki in this repository — detect the stack, agree scope + a page plan with the user, vendor the schema + check scripts + templates in one mechanical shot, seed the overview page, and wire agent entry points. Run once per repo.

2026-06-114

refresh

emyann/repolore

Bring stale wiki pages back in line with the code — diff-driven triage (re-stamp / targeted edit / rewrite), citation re-verification, index regeneration, and a reviewable commit. Use when wiki-check reports stale pages or the user asks to update/refresh the wiki.

2026-06-114

name	repolore
description	Give any repository a code-derived LLM wiki — cited claims, blob-SHA drift checking, coverage auditing, a generated index. Use when the user wants to set up, health-check, or refresh a maintained wiki / knowledge base / "lore" distilled from the codebase, or asks why-is-it-like-this documentation that stays honest as code changes.
license	MIT

repolore

<SKILL_ROOT> below means the directory containing this SKILL.md (it ships with scripts/, templates/, and references/ alongside).

Six workflows — pick by what the user asked

User intent	Procedure to read and execute
"set up a wiki / knowledge base for this repo" (once per repo)	`<SKILL_ROOT>/references/init.md`
"is the wiki up to date?" / before relying on wiki content	`<SKILL_ROOT>/references/check.md`
"update the wiki" / check reported stale pages	`<SKILL_ROOT>/references/refresh.md`
"audit the wiki for wrongness" / check's dust line reports overdue pages / "triage the findings"	`<SKILL_ROOT>/references/audit.md`
"update repolore's tooling in this repo" / check reported newer tooling	`<SKILL_ROOT>/references/update.md`
"activate repolore extras" (hook, team-wide nudge, auto-update) / after an update adds capabilities	`<SKILL_ROOT>/references/setup.md`

Read the matching procedure fully and follow it exactly, substituting <SKILL_ROOT> as defined above. Each is self-contained; the scripts they invoke are stdlib-only (node + git, no npm install).

Also available as a Claude Code plugin (/plugin marketplace add emyann/repolore), where these workflows surface as the namespaced commands /repolore:init, /repolore:check, /repolore:refresh.