agentleFS
Sign inStart free
rumi-chanrumi-chan/llm-wiki/skills/wiki-update/SKILL.md

wiki-update

Skill1 starsChanged 23 days agoMITView on GitHub

Update the shared team wiki in `docs/wiki/` for the changes on the current branch, before opening a PR. For team members (not the maintainer) - edits only the pages affected by this branch, never index.md or .sync-state. Use when the user says update the wiki for my change, document this change in the wiki, or at the end of a task in a repo that has `docs/wiki/SCHEMA.md`. For a personal `.wiki/`, use wiki-sync instead.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use claude-history-ingest, graph-colorize and 10 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.
  • Ivy-Chen1999Skill

    claude-history-ingest

    Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs.

    Also in 3 projects that use this

  • Ivy-Chen1999Skill

    graph-colorize

    Color-code the Obsidian graph view by rewriting `.obsidian/graph.json` colorGroups. Use this skill when the user says "color my graph", "color code obsidian", "colorize the graph", "color the graph by tag", "color by category", "highlight visibility in graph", "make the graph colorful", "distinguish tags in graph", or wants nodes in Obsidian's graph view tinted by tag, folder, or visibility. Generates a `colorGroups` array from the vault's actual tags/categories and merges it into the existing graph.json without clobbering other graph settings. Always backs up first.

    Also in 3 projects that use this

  • nexuschainsSkill

    cross-linker

    Scans the wiki vault and adds missing [[wikilinks]] between pages that are related but not yet connected. Use this skill when the operator says "link my pages", "find missing links", "cross-reference the wiki", "connect my wiki", "add wikilinks", or after any large ingest to weave new pages into the existing knowledge graph. Also trigger when orphaned pages need connecting or when wiki-lint reports fragmented tag clusters. This is a write-heavy skill — it modifies page files to insert links, unlike wiki-lint which only reports.

    Also in 3 projects that use this

  • nexuschainsSkill

    tag-taxonomy

    Enforces and normalizes tags across the wiki against the controlled vocabulary in wiki/schema/tag-taxonomy.md. Use this skill when the operator says "fix my tags", "normalize tags", "tag audit", "clean up tags", "tag taxonomy", or "my tags are a mess". Also use when creating or updating wiki pages and the right tags are unclear. Operates in three modes: Audit (report current state), Normalize (apply fixes), and Classify (tag a single new page). Always reads the taxonomy file before assigning any tags.

    Also in 3 projects that use this

  • jehrhardtSkill

    wiki-capture

    Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.

    Also in 3 projects that use this

  • +6 more from Ivy-Chen1999
  • +1 more from nexuschains

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Keep the team wiki true for this branch's changes, so the wiki edits travel in the same PR as the code.

    line 8
  2. Very specific:

    Read docs/wiki/SCHEMA.md and docs/wiki/index.md.

    line 16
  3. Very specific:

    Read the branch diff for context: git diff <base>...HEAD --stat, then the relevant hunks.

    line 26
  4. Very specific:

    Run node tools/wiki/wiki.mjs check --base <base> again.

    line 50
  5. Distinctive:

    Do not commit unless the user asked you to commit.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 9 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-update

Keep the team wiki true for this branch's changes, so the wiki edits travel in the same PR as the code. Small, targeted edits only: the maintainer's wiki-sync handles everything else.

1. Preconditions

  1. Project root: git rev-parse --show-toplevel. If docs/wiki/SCHEMA.md does not exist: if .wiki/SCHEMA.md exists, this is a personal wiki, so use wiki-sync; otherwise there is no wiki (suggest wiki-init). Stop.
  2. Read docs/wiki/SCHEMA.md and docs/wiki/index.md.
  3. Base branch: git symbolic-ref --short refs/remotes/origin/HEAD (e.g. origin/main), or ask. git fetch origin so the comparison is current. If the current branch is the default branch, say so: members should work on a feature branch (ask before continuing).

2. Find the pages to touch

  1. node tools/wiki/wiki.mjs check --base <base> lists:
    • drift: pages that cite files changed in this branch but were not updated;
    • problems in wiki pages already changed in this branch.
  2. Read the branch diff for context: git diff <base>...HEAD --stat, then the relevant hunks. Include uncommitted work only if the user asks.
  3. Decide whether the branch adds something significant that no page covers (a new module directory, a new protocol, a design decision worth recording).

3. Edit

For each drifted page: read it and the changed code, then fix only the sentences that became wrong or are missing. Follow the schema:

  • Minimal edits. One sentence per line. Never reflow or restyle text you are not changing.
  • Fix sources for renamed files or symbols (path or path#symbol), set updated:; set status: draft if you could not fully verify the page.

For a genuinely new topic: search first (index.md, rg -i "<term>" docs/wiki across titles and aliases). Extend an existing page if one fits; otherwise create the page at its deterministic path with full frontmatter (title, type, status, summary, aliases, sources, updated) and link it from a related page.

Never edit docs/wiki/index.md or docs/wiki/.sync-state. A new page is missing from the index until the maintainer's next sync; that is expected.

4. Check and hand back

  1. Run node tools/wiki/wiki.mjs check --base <base> again. Fix all errors. Drift warnings for pages you touched should be gone; leftover warnings about pages you deliberately left alone are fine.
  2. Do not commit unless the user asked you to commit; otherwise leave the wiki edits staged or unstaged with the code, the way the user normally works.
  3. Tell the user in two or three lines which pages changed or were created, and anything you left for the maintainer.

Download now (ZIP)

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