wiki-up — subagent knowledge-base reporter for Claude Code

A Claude Code skill that records project progress into a separate knowledge base (an Obsidian / claude-obsidian vault) via a subagent — so the calling project's context window stays clean.

You invoke it from any project. It composes a compact digest, hands that to a subagent, and the subagent does all the vault reading, note writing, and git commit/push in its own context. Your main session only sees a one-line result.

Why

When you finish a milestone in project A, you want a durable note about it in your knowledge base — but you don't want to load the entire wiki structure (index, conventions, methodology mode, related pages) into project A's context just to file one note. This skill pushes that work into a subagent.

What it does

1. Reads ~/.claude/wiki-up.config.json (vault path, backend, remote, branch, autoPush).
2. You/the agent compose a small progress digest from the current project.
3. A subagent: reads the vault conventions → writes or updates a structured wiki note (frontmatter + [[wikilinks]], routed by the vault's methodology mode) → updates hot.md + log.md → commits and pushes via scripts/wiki-up-commit-push.sh.
4. The subagent returns one line (page path + commit SHA + push status).

Install

git clone https://github.com/paipeline/wiki-up.git
cd wiki-up && bash install.sh

install.sh copies the skill to ~/.claude/skills/wiki-up and registers the auto Stop hook in ~/.claude/settings.json (idempotent; re-run to upgrade). Remove it any time with bash uninstall.sh.

Note on /plugin install. This repo carries a plugin manifest so it can be listed in a marketplace, but the auto-trigger hook is not installed by the plugin mechanism — hooks must be registered in settings.json. So install.sh is the supported path. If you install via /plugin, the /wiki-up command works but you must register the hook yourself (copy the Stop entry from install.sh) and the script paths assume ~/.claude/skills/wiki-up/.

Then configure

Easiest — just run the skill and let its setup phase ask you where the knowledge base is:

/wiki-up setup

It asks for the vault path + backend (github|gitlab|local) + remote/branch/autoPush, validates the git remote, and writes ~/.claude/wiki-up.config.json for you.

Or configure by hand:

cp wiki-up/wiki-up.config.example.json ~/.claude/wiki-up.config.json
# edit vaultPath, backend (github|gitlab|local), gitRemote, branch

First run with no config auto-enters the setup phase.

Usage

From any project:

/wiki-up a one-line description of the progress to record

or just say: "report this to my knowledge base" / "log progress to the wiki".

Backends

• github / gitlab — commit and push (uses the vault repo's existing remote + credential helper).
• local — commit only (or no git at all for a pure local Obsidian vault).

Files

• skills/wiki-up/SKILL.md — the skill instructions (the orchestration logic).
• skills/wiki-up/scripts/wiki-up-commit-push.sh — deterministic, idempotent commit+push helper.
• wiki-up.config.example.json — copy to ~/.claude/wiki-up.config.json.

Notes

• The skill records a summary, never copies source files out of the project into the vault.
• Push auth tip: if gh and your SSH key resolve to different GitHub accounts, push the vault repo over HTTPS (via the gh credential helper) to avoid 404s.

MIT