wiki-update

Syncs project knowledge into an Obsidian wiki via manifest and Git history.

4|Updated May 9, 2026
One-click install
npx skills add https://github.com/itsmarsss/memento --skill wiki-update-itsmarsss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-update
Source: https://github.com/itsmarsss/memento/tree/main/obsidian-wiki/.skills/wiki-update
Command: npx skills add https://github.com/itsmarsss/memento --skill wiki-update-itsmarsss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of losing project context by turning a codebase’s decisions, patterns, and learnings into organized Obsidian wiki pages you can reuse later.

Core Features & Use Cases

  • Project-to-wiki knowledge distillation: Scans the current project (docs, repo structure, and change history) to extract what you would want to know in the future.
  • Delta-based syncing: Uses the vault manifest to decide whether to run a full scan or only distill changes since the last synced commit.
  • Automatic page organization: Writes project-specific pages under the vault’s projects/<project-name>/ structure and places cross-project knowledge into global categories.
  • Cross-linking with correct link format: Connects new and existing wiki pages using the vault’s configured Obsidian link style.

Quick Start

Run wiki-update on your current project directory and tell it to update your Obsidian wiki when you want to distill recent progress into structured notes.

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 Obsidian automatically?

To sync project documentation into Obsidian, this skill distills architecture, decisions, and patterns from your codebase into organized wiki pages. It scans your repository and generates structured notes with provenance markers.

What is delta sync for Obsidian wiki updates?

Delta sync for Obsidian wiki updates uses a .manifest.json file to track project state, allowing the tool to distill only changes since the last Git commit. This avoids full scans and speeds up knowledge synchronization.

How do I organize project knowledge distillation into global Obsidian categories?

Project knowledge distillation organizes notes by writing project-specific pages under the vault's projects directory structure, while placing cross-project knowledge into global categories for centralized reference.

Does this knowledge distillation process respect configured Obsidian wikilink formats?

Yes, the knowledge distillation process connects new and existing wiki pages by respecting your vault's configured Obsidian wikilink format. It ensures cross-linking matches your existing note style.

Can I update multiple project wikis from different repositories into one Obsidian vault?

Yes, you can update multiple project wikis from different repositories into a single Obsidian vault. The skill applies cross-project usage, creating project and global knowledge entries based on Git history deltas.

When should I not use automated project documentation syncing?

You should avoid automated project documentation syncing when your repository lacks Git history or a valid vault manifest configuration, as the delta sync mechanism requires resolving these to track state and generate summaries.