wiki-sync

Name: wiki-sync
Availability: InStock
Author: artosetrov

Audit wiki content against backend code and detect stale data.

Updated Mar 5, 2026

Search Tags:#automation #documentation #consistency #codebase #audit #sync #wiki

Ready to run

npx skills add https://github.com/artosetrov/iron-fist-arena-backend --skill wiki-sync-artosetrov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wiki-sync
Source: https://github.com/artosetrov/iron-fist-arena-backend/tree/main/.skills/skills/wiki-sync
Command: npx skills add https://github.com/artosetrov/iron-fist-arena-backend --skill wiki-sync-artosetrov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and align the Hexbound game design wiki with the current codebase to prevent out-of-date pages and contradictions.

Core Features & Use Cases

Automatically detect changes between wiki content and source code/docs.
Identify stale data, missing pages, and contradictions, and guide updates.
Use case: maintain wiki pages that mirror backend changes to game systems, ensuring designers and engineers share a single source of truth.

Quick Start

Follow the steps to audit and align the wiki with the latest codebase in a single run.

Frequently Asked Questions about wiki-sync

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

FAQPage Schema

How do I keep my documentation wiki aligned with the live codebase?▼

Keep your wiki aligned with the live codebase by automatically detecting source code changes, comparing them against existing wiki pages, identifying stale data or missing pages, and guiding content updates to prevent documentation desynchronization.

What is the best way to audit wiki content against backend source code?▼

The best way to audit wiki content against backend source code is running an end-to-end synchronization process that detects file changes since the last sync, compares them with existing wiki pages, and flags stale data, missing pages, and contradictions for update.

How do I detect stale data and missing pages in a game design wiki?▼

Detect stale data and missing pages in a game design wiki by auditing documentation against the current backend codebase, identifying contradictions where implemented game systems no longer match the recorded design docs.

Can I automate documentation consistency checks between design docs and implementation?▼

Automate documentation consistency checks by applying a sync workflow that reads changed code files, compares them with wiki content, updates outdated pages, lints the updated documentation, and refreshes the index log to maintain a single source of truth.

What steps are needed to sync a codebase with a wiki?▼

Syncing a codebase with a wiki requires end-to-end steps: detect changes since the last sync, read the changed backend files, compare them with existing wiki pages, update outdated content, lint the pages, and refresh the index log.

Why does my game design wiki contradict the current backend implementation?▼

Your game design wiki contradicts the current backend implementation due to desynchronization that occurs when backend code changes are not reflected in the documentation, requiring an audit to detect and resolve the stale data.