wiki-stage-commit skill
✓ VerifiedReview and promote staged wiki pages from a staging directory to their final live locations after human approval.
- GitHub stars
- 3,716
- Files
- 1
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the wiki-stage-commit skill do?
wiki-stage-commit is an agent skill. Review and promote staged wiki pages from a staging directory to their final live locations after human approval.
Summary generated from the skill's SKILL.md.
About the wiki-stage-commit skill
Reviewing and promoting LLM-generated wiki pages from a staging area to a live directory is the primary function of this skill. It is designed for users who have enabled staged writes via the WIKI_STAGED_WRITES configuration in their vault. When an agent is tasked with managing a wiki, it uses this skill to present a queue of pending new pages, updates, or patches for human approval.
The process relies on the obsidian-wiki CLI to manage file inventories and atomic movements. The agent provides summaries of staged content, including metadata like confidence scores and source files, or structured diffs for patch files. Users can accept all changes, reject all changes, or perform an interactive per-file review. If a page is rejected, the skill moves it to a raw directory for manual editing. To prevent data loss, the skill uses content hashes to ensure that a page has not changed between the review and the promotion step.
What an agent can do with it
- 1Perform interactive wiki reviewReview each staged file individually to decide whether to accept or reject the proposed changes.
- 2Bulk approve staged contentAccept every file currently waiting in the staging directory without reviewing them one by one.
- 3Reject all pending writesMove all staged files to the raw directory for manual editing by rejecting them all at once.
- 4Check the staging queueList all files currently in the staging directory with a summary of their status.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the wiki-stage-commit skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the wiki-stage-commit skill in Plugin
/plugin marketplace add Ar9av/obsidian-wiki /plugin install obsidian-wiki@obsidian-wiki
Install the wiki-stage-commit skill in Claude Code
~/.claude/skills/wiki-stage-commit/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/wiki-stage-commit ~/.claude/skills/wiki-stage-commitInstall the wiki-stage-commit skill in Claude Code (project)
.claude/skills/wiki-stage-commit/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/wiki-stage-commit .claude/skills/wiki-stage-commitInstall the wiki-stage-commit skill in Codex
~/.agents/skills/wiki-stage-commit/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/wiki-stage-commit ~/.agents/skills/wiki-stage-commitInstall the wiki-stage-commit skill in Gemini CLI
~/.gemini/skills/wiki-stage-commit/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/wiki-stage-commit ~/.gemini/skills/wiki-stage-commitInstall the wiki-stage-commit skill in Claude.ai
npx degit Ar9av/obsidian-wiki/skills/wiki-stage-commit wiki-stage-commit && zip -r wiki-stage-commit.zip wiki-stage-commit # claude.ai → Customize → Skills → + → Create skill → Upload a skill → wiki-stage-commit.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablear9av/obsidian-wiki/skills/wiki-stage-commit is public and reachablegithub.com/ar9av/obsidian-wiki/tree/HEAD/skills/wiki-stage-c ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/ar9av/obsidian-wiki/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/ar9av/obsidian-wiki/blob/HEAD/skills/wiki-stage-c ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/ar9av/obsidian-wiki/blob/HEAD/skills/wiki-stage-c ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 193 linesgithub.com/ar9av/obsidian-wiki/blob/HEAD/skills/wiki-stage-c ↗Pass
SKILL.md
View on GitHubWiki 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
- Resolve config — follow the Config Resolution Protocol in
llm-wiki/SKILL.md. This givesOBSIDIAN_VAULT_PATHandWIKI_STAGED_WRITES. - If
WIKI_STAGED_WRITESis not set or isfalse, tell the user: "Staged writes mode is not enabled. SetWIKI_STAGED_WRITES=truein your.envto use this feature." Then stop. - 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
The CLI owns the inventory — don't glob _staging/ yourself:
obsidian-wiki staging list --json
Each entry carries:
| Field | Meaning |
|---|---|
staged_path |
vault-relative path of the staged file |
live_path |
where it will land (a .patch.md targets the page it is named after) |
kind |
new, update, or patch |
staged_revision |
content hash of the staged file, as you are seeing it now |
live_revision |
content hash of the live page, or null if there is none yet |
staged_mtime |
when it was staged |
Keep staged_revision and live_revision for every file you show the user. They are what makes Step 3 refuse to overwrite an agent's concurrent write instead of silently clobbering it.
Report the inventory:
Staged files: 4 new pages, 2 updates
New pages:
_staging/concepts/attention-mechanism.md (staged 2026-09-08)
_staging/entities/andrej-karpathy.md (staged 2026-09-08)
Updates:
_staging/concepts/transformer-architecture.md (target: concepts/transformer-architecture.md)
Patches:
_staging/skills/prompt-engineering.patch.md (target: skills/prompt-engineering.md)
If the list 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: live_revision no longer matches what was staged against. 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
The moves are mechanical and the CLI does them atomically. Pass the revisions from Step 1 so a decision made on stale information fails loudly.
Accepting a new page
obsidian-wiki staging promote <staged_path> \
--expect-staged <staged_revision> --expect-new
--expect-new refuses if a live page has appeared since you listed — someone else got there first.
Accepting an update
obsidian-wiki staging promote <staged_path> \
--expect-staged <staged_revision> --expect-live <live_revision>
Rejecting a file
obsidian-wiki staging discard <staged_path>
It lands in _raw/rejected-<category>-<page>.md for manual editing. An earlier rejection of the same page is never overwritten — the second becomes -2.
Accepting a patch
promote refuses .patch.md files, because merging a human-readable diff into a page whose surrounding text may have moved is judgment, not a rename. Do it yourself:
- Read the target page and the patch.
- Apply the
+additions and-deletions as a merge — never overwrite the page wholesale. - Bump the target's
updatedfrontmatter. obsidian-wiki staging discard <patch staged_path>to clear the patch from the queue.
When the CLI reports a conflict
Exit code 9 with conflict: ... on stderr means the staged or live file changed after you listed it. Nothing was moved. Do not retry with fresh revisions blindly — re-run staging list, show the user what changed, and ask again. The whole point of the check is that the content they approved is no longer the content that would land.
index.md is updated by the ingest that staged the page, so promotion does not touch it. log.md gets one STAGE_COMMIT line per invocation, written by the CLI.
Step 4: Update Tracking Files
The CLI appends the STAGE_COMMIT line to log.md itself. After processing all staged files, reconcile the index and hot cache so the promoted pages appear:
obsidian-wiki memory sync --takeaways "Committed N staged pages; rejected M." --expect-takeaways-sha256 "$TAKEAWAYS_REVISION"
(No --verb: the log line was already written by staging promote.) Never hand-edit index.md, log.md, or hot.md — the command takes the lock that keeps a parallel writer from dropping your update.
Step 5: Report
Stage commit complete.
✅ Accepted (N):
concepts/attention-mechanism.md → now live
entities/andrej-karpathy.md → now live
concepts/transformer-architecture.md → updated (patch applied)
❌ Rejected (M):
skills/fine-tuning-llms.md → moved to _raw/rejected-skills-fine-tuning-llms.md
⏭️ Skipped (K):
references/attention-is-all-you-need.md → still in _staging/
Staging queue: K files remaining
Notes
- Staged files use the same page template as live pages — they are ready to land, just awaiting approval
- Patch files use a human-readable diff format: lines starting with
+are additions, lines starting with-are deletions.staging promoterefuses them — merge them yourself (Step 3) index.mdandlog.mdare always updated immediately on ingest (they are low-risk tracking files) — only category pages go through staging- The moves live in
obsidian_wiki/staging.py; this skill supplies the judgment, not the file handling - The
_staging/directory is not tracked by Obsidian's graph view — pages only appear in the wiki after promotion
Before explicit takeaway replacement, read/reconcile the full current Key Takeaways and obtain TAKEAWAYS_REVISION from hot.takeaways_sha256 in memory status --json (llm-wiki/references/MEMORY.md). Preserve still-valid owner conclusions. Omit --takeaways for mechanical bookkeeping; stale revisions require review, not blind retry.
Files in this skill
1wiki-stage-commit skill questions
How do I install the wiki-stage-commit skill in Claude Code?
Run npx degit Ar9av/obsidian-wiki/skills/wiki-stage-commit ~/.claude/skills/wiki-stage-commit. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the wiki-stage-commit skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How do I enable staged writes?
You must set WIKI_STAGED_WRITES=true in your .env file to use this feature.
What happens to rejected wiki pages?
Rejected pages are moved to the _raw/ directory with a rejected prefix for manual editing.
Can I automatically accept all staged files?
Yes, you can use the /wiki-stage-commit --all command to accept all staged files without a per-file review.
How are patch files handled during promotion?
The promote command refuses .patch.md files; you must manually apply the additions and deletions as a merge.