wiki-rebuild
ar9av/obsidian-wiki
Archive, rebuild, or restore your wiki from scratch with full version control.
What is wiki-rebuild?
This skill manages destructive wiki operations safely by always archiving first. Use it when you want to start fresh, snapshot the current state before major changes, or restore a previous version. Supports three modes: archive-only, archive-and-rebuild, and restore-from-archive.
- Archive the current wiki state to a timestamped directory with metadata before any destructive operation
- Clear the live wiki and prepare it for full re-ingest from sources (Claude history, Codex sessions, documents)
- Restore the wiki to any previous archived state while preserving the current state as a backup
- List available archives with date, reason, page count, and source count for easy selection
- Refresh QMD search index after clearing or restoring to prevent stale results
- Log all operations to log.md with timestamps and archive references
How to install wiki-rebuild
npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-rebuild- Obsidian vault with standard directory structure (concepts/, entities/, skills/, etc.)
- Config resolution via .env, global config, or prompt setup to provide OBSIDIAN_VAULT_PATH
- Optional: QMD CLI installed if using QMD search indexing (qmd or $QMD_CLI)
How to use wiki-rebuild
- 1.Resolve your config to determine OBSIDIAN_VAULT_PATH and QMD settings
- 2.Confirm your intent: archive-only, archive-and-rebuild, or restore-from-archive
- 3.For archive-only: the skill creates a timestamped snapshot in _archives/ and logs the operation
- 4.For archive-and-rebuild: the skill archives current state, clears the live wiki, and prompts you to run ingest skills (wiki-status, claude-history-ingest, codex-history-ingest, wiki-ingest) in your chosen order
- 5.For restore: the skill lists available archives, archives the current state as a backup, restores your chosen archive, and refreshes QMD if configured
Use cases
- Before a major wiki restructure, archive the current state and rebuild from scratch to eliminate drift from sources
- Snapshot the wiki at a milestone or before experimenting with significant changes
- Restore to a known-good state if the wiki becomes corrupted or too far out of sync with sources
- Start over with a clean slate while keeping historical versions available for reference or rollback
- Knowledge workers maintaining a personal wiki or knowledge base
- Teams managing shared wiki infrastructure
- Users who want to periodically reset their wiki to source-of-truth documents
wiki-rebuild FAQ
The .obsidian/ directory is never touched. Your Obsidian configuration, plugins, and themes remain untouched during all operations.
Yes. Before any destructive operation, the skill archives the current state. You can restore from any archive in _archives/ using the restore mode.
No. After clearing the live wiki, you choose which ingest skills to run and in what order. Some sources may no longer be relevant, so you have full control.
QMD is a search index. After clearing or restoring the wiki, refresh ensures QMD forgets deleted pages and reflects the new state, preventing stale search results.
Archives are stored in $OBSIDIAN_VAULT_PATH/_archives/ as timestamped directories, each containing a full snapshot of the wiki state plus archive-meta.json with metadata.
Full instructions (SKILL.md)
Source of truth, from ar9av/obsidian-wiki.
name: wiki-rebuild description: > Archive existing wiki knowledge and rebuild from scratch, or restore from a previous archive. Use this skill when the user wants to start fresh, rebuild the wiki from all sources, archive current knowledge before a major change, or restore an older version. Triggers on "rebuild the wiki", "start over", "archive and rebuild", "restore from archive", "nuke and repave", "clean rebuild". Also use when the wiki has drifted too far from sources and incremental fixes won't cut it.
Wiki Rebuild — Archive, Rebuild, Restore
You are performing a destructive operation on the wiki. Always archive first, always confirm with the user before proceeding.
Before You Start
- Resolve config — follow the Config Resolution Protocol in
llm-wiki/SKILL.md(inline@nameoverride → walk up CWD for.env→ global config → prompt setup). This givesOBSIDIAN_VAULT_PATHand optional QMD settings such asQMD_WIKI_COLLECTION - Read
.manifest.jsonto understand current state - Confirm the user's intent. This skill supports three modes:
- Archive only — snapshot current wiki, no rebuild
- Archive + Rebuild — snapshot, then reprocess all sources from scratch
- Restore — bring back a previous archive
The Archive System
Archives live at $OBSIDIAN_VAULT_PATH/_archives/. Each archive is a timestamped directory containing a full copy of the wiki state at that point.
$OBSIDIAN_VAULT_PATH/
├── _archives/
│ ├── 2026-04-01T10-30-00Z/
│ │ ├── archive-meta.json
│ │ ├── concepts/
│ │ ├── entities/
│ │ ├── skills/
│ │ ├── references/
│ │ ├── synthesis/
│ │ ├── journal/
│ │ ├── projects/
│ │ ├── index.md
│ │ ├── log.md
│ │ └── .manifest.json
│ └── 2026-03-15T08-00-00Z/
│ └── ...
├── concepts/ ← live wiki
├── entities/
└── ...
archive-meta.json
{
"archived_at": "2026-04-06T10:30:00Z",
"reason": "rebuild",
"total_pages": 87,
"total_sources": 42,
"total_projects": 6,
"vault_path": "$OBSIDIAN_VAULT_PATH",
"manifest_snapshot": ".manifest.json"
}
Mode 1: Archive Only
When the user wants to snapshot the current state without rebuilding.
Steps:
- Create archive directory:
_archives/YYYY-MM-DDTHH-MM-SSZ/ - Copy all category directories,
index.md,log.md,.manifest.json, andprojects/into the archive - Write
archive-meta.jsonwith reason"snapshot" - Append to
log.md:- [TIMESTAMP] ARCHIVE reason="snapshot" pages=87 destination="_archives/2026-04-06T10-30-00Z" - Optionally refresh QMD if
log.mdis indexed andQMD_WIKI_COLLECTIONis configured (see "QMD Refresh After Live Wiki Changes"). - Report: "Archived 87 pages. Current wiki is untouched."
Mode 2: Archive + Rebuild
When the user wants to start fresh. This is the full sequence:
Step 1: Archive current state
Same as Mode 1 above, but with reason "rebuild".
Step 2: Clear live wiki
Remove all content from the category directories (concepts/, entities/, skills/, etc.) and the projects/ directory. Keep:
_archives/(obviously).obsidian/(Obsidian config).env(if present in vault)
Reset index.md to the empty template. Reset log.md with just the rebuild entry. Delete .manifest.json (it'll be recreated during ingest).
Step 3: Rebuild
Tell the user the vault is cleared and ready for a full re-ingest. They can now run:
wiki-status— to see all sources as "new"claude-history-ingest— to reprocess Claude historycodex-history-ingest— to reprocess Codex session historywiki-ingest— to reprocess documents and any other raw data
Each of these will rebuild the manifest as they go.
Important: Don't run the ingest yourself automatically. The user should choose what to re-ingest and in what order. Some sources may no longer be relevant.
Step 4: Log the rebuild
Append to log.md:
- [TIMESTAMP] REBUILD archived_to="_archives/2026-04-06T10-30-00Z" previous_pages=87
Refresh QMD after clearing and logging the live wiki (see "QMD Refresh After Live Wiki Changes"), then report that the vault is ready for selected re-ingest skills.
Mode 3: Restore from Archive
When the user wants to go back to a previous state.
Step 1: List available archives
Read _archives/ directory. For each archive, read archive-meta.json and present:
## Available Archives
| Date | Reason | Pages | Sources |
|---|---|---|---|
| 2026-04-06 10:30 | rebuild | 87 | 42 |
| 2026-03-15 08:00 | snapshot | 65 | 31 |
Step 2: Confirm which archive to restore
Ask the user which archive they want. Warn them that restoring will overwrite the current live wiki.
Step 3: Archive current state first
Before restoring, archive the current state (reason: "pre-restore") so nothing is lost.
Step 4: Restore
- Clear the live wiki (same as Mode 2, Step 2)
- Copy all content from the chosen archive back into the live wiki directories
- Restore
index.md,log.md, and.manifest.jsonfrom the archive - Append to
log.md:- [TIMESTAMP] RESTORE from="_archives/2026-03-15T08-00-00Z" pages_restored=65
Step 5: Report
Refresh QMD after restore (see "QMD Refresh After Live Wiki Changes"), then tell the user what was restored and suggest running wiki-lint to check for any issues with the restored state.
QMD Refresh After Live Wiki Changes
QMD is a search index, not the source of truth. If QMD refresh fails, do not roll back archive, rebuild, or restore work; report the failure and leave the markdown vault intact.
GUARD: If $QMD_WIKI_COLLECTION is empty or unset, skip this step.
When to run:
| Mode | Refresh QMD? | Reason |
|---|---|---|
| Archive only | Optional | Live wiki content is unchanged except log.md; refresh if log.md is indexed and QMD is configured. |
| Archive + Rebuild | Required after clearing live wiki | QMD must forget deleted pages or it will return stale search results. Later ingest skills will refresh again as sources are reprocessed. |
| Restore | Required after restore | The live wiki was replaced with archive content, so QMD must match the restored state. |
This refresh currently requires the local QMD CLI. Use $QMD_CLI if set; otherwise use qmd. If the CLI is unavailable, report QMD skipped: qmd CLI unavailable.
For CLI refresh:
${QMD_CLI:-qmd} update
If the output says new hashes need vectors, or if restore replaced live pages and embeddings may be stale, run:
${QMD_CLI:-qmd} embed
Verify the wiki collection reflects the operation:
${QMD_CLI:-qmd} ls "$QMD_WIKI_COLLECTION"
For restore, also verify one restored page if the archive has a known page path:
${QMD_CLI:-qmd} get "qmd://$QMD_WIKI_COLLECTION/<restored-page>.md" -l 5
Record QMD refresh in the final report as one of:
QMD refreshed: update + embed + verifiedQMD refreshed: update only + verifiedQMD skipped: QMD_WIKI_COLLECTION unsetQMD skipped: archive-only live content unchangedQMD skipped: qmd CLI unavailableQMD failed: <short error summary>
Safety Rules
- Always archive before destructive operations. No exceptions.
- Always confirm with the user before clearing the live wiki.
- Never delete archives unless the user explicitly asks. Archives are cheap insurance.
- The
.obsidian/directory is sacred. Never touch it during archive/rebuild/restore — it contains the user's Obsidian settings, plugins, and themes. - If something goes wrong mid-rebuild, the archive is there. Tell the user they can restore.
Related skills
More from ar9av/obsidian-wiki and the wider catalog.

wiki-research
Autonomously research topics via multi-round web search and file structured results into your Obsidian wiki.

wiki-setup
Initialize a new Obsidian wiki vault with structure, config, and special files.

wiki-stage-commit
Review and promote staged wiki pages to their final locations with human approval.

wiki-status
Show wiki ingestion status, delta since last ingest, and vault structure insights.

wiki-switch
Switch between multiple Obsidian wiki vault profiles with named configs.

wiki-synthesize
Discover and synthesize cross-cutting insights from concept pairs that co-occur across your Obsidian wiki.