wiki-sync

Synchronize merged pull requests into a zone-based team wiki.

3|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/zoraxl/team-brain --skill wiki-sync-zoraxl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-sync
Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/wiki-sync
Command: npx skills add https://github.com/zoraxl/team-brain --skill wiki-sync-zoraxl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation between implementation and documentation by automating the synchronization of merged PRs into a structured, zone-based wiki, ensuring that architectural decisions and product knowledge remain current and authoritative.

Core Features & Use Cases

  • Automated ADR Management: Automatically creates or updates Architecture Decision Records (ADRs) based on PR metadata and plan files.
  • Lifecycle Tracking: Manages the transition of ideas from brainstorming through implementation to archival, maintaining a clear audit trail.
  • Zone-Aware Synthesis: Intelligently routes knowledge to appropriate wiki zones (product, platform, or general) based on implementation scope.

Quick Start

Use the wiki-sync skill to ingest the changes from the recently merged pull request number 1234 into the team wiki.

Frequently Asked Questions about wiki-sync

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

FAQPage Schema
How do I automate wiki updates from merged pull requests?

Automated wiki updates from merged pull requests are handled by synchronizing PR metadata and source documentation into a structured, zone-based team wiki. The skill generates ADRs, updates product documentation, and archives planning artifacts.

How does ADR lifecycle management work for repository changes?

ADR lifecycle management works by tracking architectural decisions from brainstorming through implementation to archival. It automatically creates or updates Architecture Decision Records based on merged PR metadata and plan files to maintain a clear audit trail.

Do I need GitHub CLI to synchronize documentation into a team wiki?

Yes, GitHub CLI integration is required to synchronize documentation into a team wiki. The skill relies on GitHub CLI to access merged pull requests and source documentation across implementation repositories for knowledge ingestion.

What is zone-based wiki routing for product and platform knowledge?

Zone-based wiki routing is the process of directing ingested knowledge to appropriate wiki zones such as product, platform, or general. Routing is determined automatically based on the implementation scope of the merged changes.

How do I ingest a specific merged pull request into the team wiki?

You can ingest a specific merged pull request by providing the PR number to the skill. It then processes the changes, generates corresponding ADRs, updates relevant product documentation, and archives completed planning artifacts.

What are the limitations of automated wiki synchronization?

A key limitation is the strict adherence to a defined wiki-zone architectural model for all knowledge ingestion. Additionally, the automation operates across implementation repositories and requires GitHub CLI, limiting use outside this structural model.