Wiki Stage Commit
Human-in-the-loop approve or reject LLM-written Obsidian wiki pages staged under _staging/ before they go live.
Overview
wiki-stage-commit is an agent skill for the Build phase that reviews LLM pages in _staging/ and promotes accepted files to live wiki paths when WIKI_STAGED_WRITES=true.
Install
npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-stage-commitWhat is this skill?
- Interactive /wiki-stage-commit review: accept or reject each file in _staging/
- Flags --all, --reject-all, and --list for bulk accept, bulk reject to _raw/, or inventory only
- Requires WIKI_STAGED_WRITES=true; stops with clear message when staged mode is off
- Resolves vault path via llm-wiki Config Resolution Protocol before touching files
- Rejected staged pages return to _raw/ for manual editing instead of silent publish
Adoption & trust: 537 installs on skills.sh; 1.8k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Agent-generated wiki pages are sitting in _staging/ and you do not want them published without a per-file accept or reject decision.
Who is it for?
Solo operators using obsidian-wiki with staged writes who batch-generate docs then approve promotions in one session.
Skip if: Vaults without WIKI_STAGED_WRITES=true or teams that publish wiki changes directly without a staging directory.
When should I use this skill?
WIKI_STAGED_WRITES=true and user says /wiki-stage-commit, review staged pages, commit staged writes, promote staged pages, approve staged changes, or what's waiting in staging.
What do I get? / Deliverables
Accepted staged pages land in final wiki locations; rejected ones move to _raw/ for manual fixes, keeping the live vault trustworthy.
- Promoted wiki pages at final paths
- Rejected files relocated to _raw/
- Staging inventory summary when using --list
Recommended Skills
Journey fit
Canonical shelf is Build docs because it governs how agent-authored wiki content lands in the vault. Docs subphase fits staged write promotion, accept/reject review, and final path moves in a knowledge base.
How it compares
Wiki promotion workflow for Obsidian vaults, not a generic git stage-and-commit skill.
Common Questions / FAQ
Who is wiki-stage-commit for?
Builders maintaining an Obsidian LLM wiki who enable staged writes and want explicit human approval before pages go live.
When should I use wiki-stage-commit?
After agent wiki writes complete, when you run /wiki-stage-commit, or when you ask to review staged pages, commit staged writes, or list what is waiting in staging.
Is wiki-stage-commit safe to install?
It moves and deletes staged files in your vault—review Security Audits on this page, back up the vault, and confirm paths before using --all or --reject-all.
Workflow Chain
Requires first: skill ar9av obsidian wiki llm wiki
SKILL.md
READMESKILL.md - Wiki Stage Commit
# Wiki Stage Commit — Staged Write Promotion 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. ## Before You Start 1. **Resolve config** — follow the Config Resolution Protocol in `llm-wiki/SKILL.md`. This gives `OBSIDIAN_VAULT_PATH` and `WIKI_STAGED_WRITES`. 2. If `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. 3. Read the `_staging/` directory inventory. ## Invocation Forms ``` /wiki-stage-commit # interactive review: show each file and ask accept/reject /wiki-stage-commit --all # accept all staged files without per-file review /wiki-stage-commit --reject-all # reject all staged files (move to _raw/ for manual editing) /wiki-stage-commit --list # list staged files with summary, no changes ``` ## Step 1: Inventory Staged Files 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: ``` Staged files: 4 new pages, 2 updates New pages: _staging/concepts/attention-mechanism.md (ingested 2 days ago) _staging/entities/andrej-karpathy.md (ingested 2 days ago) _staging/skills/fine-tuning-llms.md (ingested yesterday) _staging/references/attention-is-all-you-need.md (ingested 3 hours ago) Updates (patch files): _staging/concepts/transformer-architecture.patch.md (target: concepts/transformer-architecture.md) _staging/skills/prompt-engineering.patch.md (target: skills/prompt-engineering.md) ``` If `_staging/` is empty, report: "Nothing staged. All writes have been committed or no staged writes have been produced yet." ## Step 2: Per-File Review (interactive mode) For each staged file (new pages first, then updates): ### For new pages: Display a summary: ``` --- 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]? ``` ### For patch files: Display a structured diff: ``` --- 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]? ``` 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). ## Step 3: Apply Decisions ### Accepting a new page 1. Move `_staging/<category>/page.md` → `<category>/page.md` (the final location) 2. Update `index.md` with the ne