wiki-stage-commit

Review and promote staged wiki pages to their final vault locations.

Updated Nov 9, 2023
One-click install
npx skills add https://github.com/oresttokovenko/dot-files --skill wiki-stage-commit-oresttokovenko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-stage-commit
Source: https://github.com/oresttokovenko/dot-files/tree/main/chezmoi/dot_agents/skills/wiki-stage-commit
Command: npx skills add https://github.com/oresttokovenko/dot-files --skill wiki-stage-commit-oresttokovenko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated wiki pages written to a staging area need human review before going live, and manually moving files risks overwriting concurrent edits or losing track of what was approved. This Skill provides a structured review-and-promote workflow for staged Obsidian wiki pages. ## Core Features & Use Cases - Staged Inventory: Lists all staged pages via the obsidian-wiki CLI with kind (new, update, patch), content revisions, and target paths. - Interactive Review: Shows summaries, previews, and structured diffs per file, letting you accept, reject, or skip each one; supports --all, --reject-all, and --list batch modes. - Conflict-Safe Promotion: Passes expected staged and live revisions to the CLI so promotion fails loudly (exit code 9) if content changed since listing, instead of silently clobbering concurrent writes. - Use Case: After an ingest run stages four new concept pages and two patches, run the skill to review each page, accept the good ones into the live wiki, and send rejected drafts to _raw/ for manual editing. ## Quick Start Ask the assistant to review staged pages and commit staged writes in the wiki vault.

Frequently Asked Questions about wiki-stage-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review and approve staged wiki pages before publishing?

Run the wiki-stage-commit skill to list staged files via obsidian-wiki staging list, then review each page interactively with accept, reject, or skip options. Accepted pages are promoted to their live paths; rejected ones move to _raw/ for manual editing.

How do I accept all staged wiki pages at once?

Invoke the skill with the --all flag to accept every staged file without per-file review. Use --reject-all to discard everything to _raw/, or --list to only print the inventory without making changes.

What happens if a wiki page changes while it is staged?

The promote command checks expected staged and live revisions; if either changed since listing, the CLI exits with code 9 and a conflict message, moving nothing. Re-run staging list, show the user what changed, and ask for a fresh decision.

Can I promote a .patch.md file directly to the live wiki?

No, the promote command refuses .patch.md files because merging a diff into a page whose text may have moved requires judgment. Read the target page and patch, apply additions and deletions as a merge, bump the updated frontmatter, then discard the patch.

When is the staged writes workflow available?

Staged writes only work when WIKI_STAGED_WRITES=true is set in the vault's .env config. If it is unset or false, the skill reports that staged writes mode is not enabled and stops.