wiki-review

Arbitrate wiki proposals and apply merge, rewrite, discard, or defer decisions.

5|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/rbah31/claude-code-workflow --skill wiki-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-review
Source: https://github.com/rbah31/claude-code-workflow/tree/main/.claude/skills/wiki-review
Command: npx skills add https://github.com/rbah31/claude-code-workflow --skill wiki-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill arbitrates proposed wiki additions accumulated under briefs/wiki-proposals. It ensures a controlled, human-validated path for updating the wiki by enforcing gate rules and providing a clear decision workflow.

Core Features & Use Cases

  • Proposal discovery and validation: inventories briefs/wiki-proposals, skipping non-proposal files and subdirectories.
  • Decision workflow: walks each proposal in date order, summarizes intent, and prompts for merge as-is, rewrite, discard, or defer.
  • Safe write gate and cleanup: creates a temporary sentinel, writes approved content to the wiki path, removes the proposal, and clears the sentinel to re-enable the gate for subsequent runs.

Quick Start

Start a wiki review session to walk through all briefs/wiki-proposals and apply merge, rewrite, discard, or defer decisions.

Frequently Asked Questions about wiki-review

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

FAQPage Schema
How do I review and approve multiple wiki proposals before merging them?

To review wiki proposals, the Skill inventories files under briefs/wiki-proposals, summarizes each proposal's intent in date order, and prompts you to decide whether to merge as-is, rewrite, discard, or defer each entry.

What is a wiki gate workflow for content management?

A wiki gate workflow enforces a single human-validated path for updating wiki content by creating a temporary sentinel file, writing approved proposals to the target path, and cleaning up both the proposal and sentinel upon completion.

How do I manage wiki content updates so only reviewed changes get published?

You manage wiki updates by arbitrating accumulated proposals through a decision workflow that requires explicit human review, ensuring only approved content is written to the wiki path while unreviewed proposals remain deferred or discarded.

Can I defer wiki proposals and review them later in a governance process?

Yes, the review workflow supports deferring proposals, allowing you to skip specific entries during a wiki gate session and revisit them later while processing other accumulated proposals in date order.

What happens to a wiki proposal after I approve it for merging?

After you approve a proposal, the Skill writes its content to the target wiki path, removes the original proposal file from briefs/wiki-proposals, and deletes the active sentinel file to re-enable the gate for subsequent runs.

How do I ensure only one wiki content review session is active at a time?

The Skill enforces a single legitimate path through the wiki gate by creating a temporary sentinel file at .claude/.wiki-review-active, preventing concurrent sessions and removing the sentinel only when the review is complete.