wiki-update

Sync and summarize project knowledge into an Obsidian wiki.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires obsidian, git, markdown, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps automate the process of syncing and distilling project knowledge into your Obsidian wiki, reducing manual effort and ensuring consistent knowledge capture.

Core Features & Use Cases

  • Project Knowledge Synthesis: Converts project insights and codebase details into wiki pages.
  • Automatic Updates: Detects changes in the project and updates the wiki accordingly.
  • Structured Output: Creates a well-organized and categorized wiki for easy reference.

Quick Start

To update your wiki, use the "wiki-update" command with the current project directory.

Frequently Asked Questions about wiki-update

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

FAQPage Schema
How do I automatically sync project knowledge to an Obsidian wiki?

To automatically sync project knowledge to an Obsidian wiki, you can use document automation to scan Markdown and source code directories, summarizing codebase details into structured wiki pages.

Does the Obsidian wiki update support delta updates or full project scans?

Yes, the Obsidian wiki update supports both full project scans and delta updates, allowing you to detect specific codebase changes and update only the modified wiki pages accordingly.

What do I need to set up before using project knowledge synthesis for Obsidian?

To use project knowledge synthesis for Obsidian, you need Git, a Markdown directory structure, and an understanding of your project layout to ensure provenance tracking and link building operate correctly.

How does provenance tracking work when updating Markdown wiki pages?

Provenance tracking works during wiki updates by mapping the summarized project knowledge directly back to the original source code directories, ensuring every generated Markdown wiki page maintains clear traceability.

Can I run a full project scan on a large codebase to generate wiki pages?

Yes, you can run a full project scan on a codebase to generate wiki pages, but you must ensure your Git and Markdown directory structures are properly organized for the synthesis process to categorize the outputs effectively.

What is the best way to distill codebase details into structured Markdown documentation?

The best way to distill codebase details into structured Markdown documentation is by automating project knowledge synthesis, which converts source code directories into categorized Obsidian wiki pages with link building.