wiki-fold

Roll up append-only wiki log entries into compact traceable fold meta-pages.

10.6k|1.2k|Updated Apr 7, 2026

Search Tags:#knowledge management #obsidian #idempotency #extractive summarization #wiki rollup #git-safe commits

Ready to run

npx skills add https://github.com/AgriciDaniel/claude-obsidian --skill wiki-fold

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wiki-fold
Source: https://github.com/AgriciDaniel/claude-obsidian/tree/main/skills/wiki-fold
Command: npx skills add https://github.com/AgriciDaniel/claude-obsidian --skill wiki-fold

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It converts a long, append-only wiki/log.md history into compact meta-pages that are guaranteed to be traceable back to the underlying log entries, so you can skim progress without losing auditability.

Core Features & Use Cases

Extractive log rollups: generates fold content only from log entries and bounded referenced pages, with no invented synthesis.
Structural idempotency: derives deterministic fold IDs from range and k, preventing accidental duplicate fold writes.
Safe dry-run and commit mode: supports stdout-only preview by default, with a protected commit workflow that updates wiki/folds/, wiki/index.md, and wiki/log.md.

Quick Start

Ask the AI to run wiki-fold in dry-run mode for k=4 so it prints the fold page content that would be committed.

Frequently Asked Questions about wiki-fold

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

FAQPage Schema

How do I summarize wiki log entries without losing traceability to the original records?▼

To summarize wiki log entries without losing traceability, you can roll up append-only log histories into compact fold meta-pages. This process guarantees every generated fold page links directly back to the underlying log entries.

How do I generate deterministic and idempotent rollups of recent Obsidian log ranges?▼

To generate idempotent rollups of recent Obsidian log ranges, derive deterministic fold IDs from the range and k value. This structural idempotency prevents accidental duplicate fold writes during the rollup process.

Can I preview extractive summarization of markdown logs before committing changes to my wiki?▼

Yes, you can preview extractive summarization safely using a dry-run mode that outputs fold content to stdout by default. This prevents accidental modifications until you explicitly use the protected commit workflow.

What is the best way to enforce no-invention extractive rules for knowledge management logs?▼

The best way to enforce no-invention extractive rules for knowledge management logs is to strictly bound the summarization scope. Generate fold content only from existing log entries and referenced pages, ensuring no invented synthesis is added.

Does wiki-fold support Git-safe commits for Obsidian workflows?▼

Yes, wiki-fold supports Git-safe commits through its protected commit workflow. When explicitly triggered, it deterministically updates the wiki folds directory, index file, and main log file without unintended side effects.

What happens if I run multiple rollups on the same log range with identical parameters?▼

Running multiple rollups on the same log range with identical parameters yields identical results due to deterministic fold ID derivation. This structural idempotency ensures no duplicate fold pages are accidentally written.