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

wiki-history

Skill1 starsChanged 7 months agoMITView on GitHub

Use when the user runs /history <page> [--diffs], says "how did this page evolve", "show me the history of [[X]]", or wants a narrated timeline of a single page's commits. Classifies each commit (creation / expansion / maintenance / rename) and narrates. Read-only.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If --diffs passed, after each narrated commit, inline its diff:

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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-history

Narrates the commit history of a single wiki page.

Refuse conditions

  1. No .llm-wiki.yaml in CWD or ancestors.
  2. git log --follow -- <page> returns empty and <page> is not in the working tree — the page never existed.

Workflow

1. Pull the log

git log --follow --format="%H %ai %s" --reverse -- <page>
git log --follow --name-status --diff-filter=R -- <page>

First query yields SHA + date + subject per commit. Second detects rename boundaries (entries marked R<score>).

2. Classify each commit

SignalClass
git show --stat <sha> lists the page as create modeCreation
Scope ingest(<slug>), not creationExpansion via ingest
Scope revise(<slug>), not creationHuman revision
Scope lint(<date>)Maintenance
Rename flag from second queryRename (record old and new path)
Scope bootstrap:Scaffolding

3. Narrate

Single paragraph, forward-chronological. Include short SHAs and dates. Quote revise commit bodies when non-trivial.

Example shape:

wiki/concepts/memex.md — <N> commits, <first-date> to <last-date>.

Created during ingest(karpathy-llm-wiki) on 2026-04-12 (a1b2c3d). Expanded during ingest(bush-as-we-may-think) on 2026-04-15 (e4f5g6h) with the Bush-1945 lineage. Contradiction with [[llm-wiki]] flagged and resolved during lint(2026-04-20) (i7j8k9l). Revised on 2026-04-20 (m0n1o2p, revise(memex): "clarified selection-by-association").

4. Current-state footer

Always append:

Status: <frontmatter.status>
Updated: <frontmatter.updated>
Sources: [<frontmatter.sources>]
Inbound links: <count from `git grep -l "\[\[<slug>\]\]" -- 'wiki/**/*.md' | wc -l`>
Outbound links: <count of [[X]] in page body>

5. Optional --diffs

If --diffs passed, after each narrated commit, inline its diff:

git show <sha> -- <page>

Notes

  • Short SHAs (7 chars) in narration.
  • Dates ISO 8601.
  • Rename cases use the new path for subsequent commits but name the old path at the rename boundary.

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. sbluemin/fleet-harness★ 17same 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.

  • 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.

Reviews can't be read right now.

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