npx skills add ...
npx skills add ar9av/obsidian-wiki --skill wiki-stage-commit
npx skills add ar9av/obsidian-wiki --skill wiki-stage-commit
Review and promote staged wiki pages to their final locations. Use when WIKI_STAGED_WRITES=true and the user says "/wiki-stage-commit", "review staged pages", "commit staged writes", "promote staged pages", "approve staged changes", or "what's waiting in staging". Shows each staged file, lets the user accept or reject it, and moves accepted files to their final wiki locations. Rejected files are moved back to _raw/ for manual editing.
You are reviewing LLM-written pages that are waiting in _staging/ for human approval before they land in the live wiki. This skill is only useful when WIKI_STAGED_WRITES=true in the vault config.
llm-wiki/SKILL.md. This gives OBSIDIAN_VAULT_PATH and WIKI_STAGED_WRITES.WIKI_STAGED_WRITES is not set or is false, tell the user: "Staged writes mode is not enabled. Set WIKI_STAGED_WRITES=true in your .env to use this feature." Then stop._staging/ directory inventory.Glob $OBSIDIAN_VAULT_PATH/_staging/**/*.md — these are the pending pages.
Also glob $OBSIDIAN_VAULT_PATH/_staging/**/*.patch.md — these are pending updates to existing pages (diff-style files showing proposed additions and deletions).
Report the inventory:
If _staging/ is empty, report: "Nothing staged. All writes have been committed or no staged writes have been produced yet."
For each staged file (new pages first, then updates):
Display a summary:
Display a structured diff:
If --all flag is set, skip prompting and accept every file.
If --reject-all flag is set, skip prompting and reject every file.
If --list flag is set, stop after printing the inventory (Step 1).
_staging/<category>/page.md → <category>/page.md (the final location)index.md with the new page entryupdated frontmatter timestampindex.md if the summary changedMove it to $OBSIDIAN_VAULT_PATH/_raw/ for manual editing:
_staging/concepts/page.md → _raw/rejected-concepts-page.md_staging/concepts/page.patch.md → _raw/rejected-patch-concepts-page.mdrejected- so the user can identify itBefore applying a patch, check whether the target page's updated frontmatter is newer than the patch file's own updated field:
⚠️ Conflict: target was updated since this patch was staged. Applying may lose recent changes.Apply anyway [y], Skip [s], Reject [r]?After processing all staged files:
hot.md — update the Recent Activity section: "Committed N staged pages; rejected M."log.md — append:
+ are additions, lines starting with - are deletionsindex.md and log.md are always updated immediately on ingest (they are low-risk tracking files) — only category pages go through staging_staging/ directory is not tracked by Obsidian's graph view — pages only appear in the wiki after promotion--- New page: concepts/attention-mechanism.md ---
Title: Attention Mechanism
Tags: #ml #architecture
Summary: Core building block of transformers — computes weighted sum of values based on query-key similarity.
Tier: supporting
Confidence: 0.72
Sources: papers/attention.pdf
[Preview first 20 lines of body]
...
Accept [a], Reject [r], Skip [s], Preview full [p]?--- Update: concepts/transformer-architecture.md ---
Source: _staging/concepts/transformer-architecture.patch.md
Proposed additions (+):
+ Transformers outperform RNNs on tasks requiring long-range dependencies. ^[inferred]
+ New source: papers/survey-2026.pdf
Proposed deletions (-):
- The attention mechanism was first described in [Bahdanau 2015]. (to be replaced by updated claim)
⚠️ Conflict check: target page was modified 3 days after staging. Review carefully.
Accept [a], Reject [r], Skip [s], Preview full diff [p]?