wiki-update

Distill project architecture and decisions into Obsidian wiki pages.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Nero-kk/claude-agent-skills --skill wiki-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-update
Source: https://github.com/Nero-kk/claude-agent-skills/tree/main/claude-skills/wiki-update
Command: npx skills add https://github.com/Nero-kk/claude-agent-skills --skill wiki-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a project's scattered signals—architecture notes, rationale, and meaningful changes—into searchable wiki pages so you can find context later without reading diffs or commit histories.

Core Features & Use Cases

  • Delta-aware synchronization: Detects first-time vs incremental syncs and focuses on meaningful changes since the last committed sync.
  • Knowledge distillation: Extracts architecture decisions, key abstractions, dependencies, trade-offs, and lessons learned and formats them into pages with YAML frontmatter and provenance markers.
  • Merge-first workflow & tracking: Merges updates into existing pages to avoid duplicates, updates the vault index and manifest, and appends audit entries to the sync log.
  • Use Case: Run after a release, major refactor, or before handoff to capture design rationale and onboarding material for future contributors.

Quick Start

Say "update wiki" while in your project directory to distill the project's knowledge and push merged pages into your Obsidian vault.

Frequently Asked Questions about wiki-update

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

FAQPage Schema
How do I sync project documentation into an Obsidian vault automatically?

Sync project documentation into an Obsidian vault by distilling architecture decisions and meaningful git changes into wiki pages. Use the wiki-update command from any project directory to merge updates into existing pages with proper YAML frontmatter and provenance markers.

What is the best way to capture architecture decisions and rationale for project onboarding?

Capturing architecture decisions and rationale for onboarding is done by extracting key abstractions, dependencies, and trade-offs from your project directory. The knowledge distillation process formats this context into searchable wiki pages, preventing the need to read commit histories later.

Does syncing project knowledge to Obsidian require git history?

Syncing project knowledge to Obsidian does require git history to detect meaningful changes since the last committed sync. Delta-aware synchronization uses this git history to focus on incremental updates rather than duplicating previously synced information.

Can I update my Obsidian wiki pages without creating duplicates?

You can update Obsidian wiki pages without duplicates by using a merge-first workflow. This process merges new updates into existing pages, updates the vault index and manifest, and appends audit entries to the sync log to ensure provenance tracking.

Do I need an OBSIDIAN_VAULT_PATH to sync project knowledge to Obsidian?

You need an OBSIDIAN_VAULT_PATH and the vault's .manifest.json file to sync project knowledge to Obsidian. These prerequisites allow the synchronization logic to locate your vault and correctly merge distilled project context into the wiki structure.

When should I run a wiki sync for my project knowledge?

You should run a wiki sync for your project knowledge after a release, major refactor, or before handoff. Running the synchronization at these milestones captures design rationale and onboarding material for future contributors when context changes are most meaningful.