agentleFS
Sign inStart free
justvinhherejustvinhhere/llm-wiki-plugin/skills/wiki-review/SKILL.md

wiki-review

Skill1 starsChanged 7 months agoMITView on GitHub

Use when the user runs /review, says "show pending changes", "what's uncommitted", or wants an audit of uncommitted wiki edits before they land in history. Narrates uncommitted changes, flags structural issues scoped to those changes, and commits them with a conventional subject. Fully automatic.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If any flag fires, list them.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

wiki-review

Audits and commits the uncommitted diff on wiki paths. Intended for hand-edits or mid-ingest interruptions; a normal /ingest already commits on its own.

Refuse conditions

  1. No .llm-wiki.yaml in CWD or ancestors.
  2. .llm-wiki.yaml:schema_version != 1.
  3. Working tree clean on wiki/ and index.md — nothing to review.

Workflow

1. Narrate the diff

  • git status -- wiki/ index.md raw/
  • git diff --stat -- wiki/ index.md
  • For each changed file, git diff <file> and report:
    • Changed sections (heading / frontmatter / list / prose).
    • Frontmatter invariants: updated: bumped to today; sources: appended not replaced; contradictions: entries well-shaped.
    • Literal change narration for hand-edits; no inferred motivation.

2. Structural flags scoped to changed files

Using the resolution rules in skills/wiki-ingest/reference.md:

  • New dead [[link]] (zero hits).
  • New ambiguous [[link]] (multiple hits).
  • New orphan page (created without any inbound link and not covered by lint.orphan_allowlist).
  • New contradictions: entries.
  • Index drift: new page missing from index.md, or an index entry pointing to a now-missing page.

If any flag fires, list them. They do not block the commit.

3. Pick commit scope

  • Single file under wiki/ → revise(<page-slug>): <first-heading-of-diff-or-filename>.
  • Multi-file under wiki/ → revise(multi): <count> page(s).
  • Includes .llm-wiki.yaml or other config changes → split: commit wiki changes first with a wiki scope, then commit config with chore: <summary>.
  • Includes raw/ additions without a corresponding wiki/sources/<slug>.md → refuse: raw without a source page means an ingest was interrupted; run /ingest to complete it.

4. Commit

git add <explicit-paths>
git commit -m "<scope>: <subject>"

Never git add ..

Output

Single block:

Reviewed <N> file(s). Flags: <count or "none">. Committed as <short-sha> <scope>: <subject>.

Download now (ZIP)

  • Other versions9 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 9

    1. IssacW228/student-llm-wiki★ 173same name
    2. VintLin/zettelkasten★ 4same name
    3. k79k06k02k/llm-project-wiki★ 2same name
    4. dexio-wiki/llm-wiki-skills★ 1same name
    5. hmjBill/skills★ 1same name
    6. nathanaday/almagest★ 1same name
    7. nathanaday/atlas-obsidian★ 1same name
    8. nathanaday/claude-atlas★ 1same name
    9. boaz-hwang/boaz-wiki★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use almagest, almagest-onboard and 9 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • nathanadaySkill

      almagest

      Orient in the Almagest vault, say what waits for the user, do the work a request asks in a linked repository, and route any other request to the skill that owns it. Use for /almagest, what is going on, status, what waits for me, where do I work on X, work on X, fix this, implement, build, note this, remember to, publish my journal, what is in my journals, and any request when the right skill is not clear. Keeping part of this conversation is wiki-save; files to learn from are wiki-ingest.

      Also in 3 projects that use this

    • nathanadaySkill

      almagest-onboard

      Make a new Almagest vault: ask its name, its folder, and how freely to tag, then link its first repositories. Use for set up almagest, new vault, start a vault here, onboard, make this folder a vault. Linking a repository to a vault that exists is repo-link.

      Also in 3 projects that use this

    • suwonleeeSkill

      wiki-save

      Session close-out (warm, O(this session)) — file THIS session into the log, consolidate its durable concepts into the topic encyclopedia (5_topic), refresh L0 (current-state), finish with overview·lint. The every-session habit; volume work (backlog · review · gaps · re-distill) defers to the periodic `/wiki-deep` deep pass

      Also in 3 projects that use this

    • richard-kim-79Skill

      wiki-sync

      Organizes research notes into a structured wiki knowledge base with wikilinks ([[slug]] syntax), cross-references, and an auto-generated index. Use when the user asks to build a wiki, organize notes into a knowledge base, create an index, or sync notes into a structured format.

      Also in 3 projects that use this

    • +7 more from nathanaday
  • In this repository6 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free