wiki-update

Distill project knowledge into structured Obsidian wiki pages with provenance tracking.

Updated Nov 9, 2023
One-click install
npx skills add https://github.com/oresttokovenko/dot-files --skill wiki-update-oresttokovenko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-update
Source: https://github.com/oresttokovenko/dot-files/tree/main/chezmoi/dot_agents/skills/wiki-update
Command: npx skills add https://github.com/oresttokovenko/dot-files --skill wiki-update-oresttokovenko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project knowledge—architecture decisions, design rationale, and hard-won patterns—gets lost in git history and code. This Skill syncs what you've been working on into your Obsidian wiki so you can rediscover it months later without re-deriving the reasoning. ## Core Features & Use Cases - Delta-aware syncing: Tracks the last synced commit per project in .manifest.json, detects rebases or force-pushes, and falls back to a full scan when history is unreachable. - Structured distillation: Creates project overview pages plus concept, skill, and reference pages with YAML frontmatter, provenance markers (extracted/inferred/ambiguous), and confidence scores. - Cross-linking and tracking: Updates index.md, log.md, and hot.md, adds wikilinks between related pages, and optionally refreshes a QMD search index. - Use Case: After finishing a feature in any repo, say "update wiki" and the Skill scans the project, computes what changed since the last sync, and writes distilled architecture notes into your vault. ## Quick Start From any project directory, ask the assistant to update your wiki with what you've been working on, optionally naming a vault like "@work update wiki".

Frequently Asked Questions about wiki-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync a project to my Obsidian wiki?

Run the skill from any project directory by saying "update wiki" or "sync to wiki". It resolves your vault path from config, scans the project, computes changes since the last sync, and writes distilled pages into the vault.

How does wiki sync track what has already been synced?

A `.manifest.json` file in the vault records each project's source repo, last sync timestamp, and last synced commit SHA. On subsequent runs the skill diffs `git log` from that commit to HEAD to process only new changes.

What happens if the branch was rebased since the last wiki sync?

The skill checks whether the stored commit is still an ancestor of HEAD using `git merge-base`. If the SHA is unreachable due to a rebase or force-push, it warns you and falls back to a full scan, then updates the stored SHA.

Can I use wiki-update with multiple Obsidian vaults?

Yes, inline named-vault routing like "@work update wiki" is supported through the shared Config Resolution Protocol. Config resolves from the inline override, then a local `.env`, then global config.

What content should not be distilled into the wiki?

Skip file listings, boilerplate, dependency versions, lock files, and isolated bug fixes. The heuristic is: if reading the codebase answers the question, don't wiki it; only capture reasoning you'd otherwise re-derive from git history.