Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ar9av/wiki-stage-commit
Review and promote staged wiki pages to their final locations.
Passed 13 of 17 test cases with the skill, and 6 of 17 without it.
and 10 more in the full report
9 fixed8 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I reviewed a staged file `_staging/concepts/outdated-idea.md` and decided to reject it. Where does the rejected draft get placed, and what CLI subcommand handles the rejection?
| Checked | Without skill | With skill |
|---|---|---|
| Uses obsidian-wiki staging discard to process the rejected staged file. | Missed | Passed |
| Moves the rejected file to the _raw/ directory with a rejected- prefix. | Missed | Passed |
The instructions your model reads when the skill loads.
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./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
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.
test cases passed, vs 6 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.