wiki-maintenance

Map code changes to GitHub wiki pages and enforce update workflows.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill wiki-maintenance-agnaldo4j
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-maintenance
Source: https://github.com/agnaldo4j/kanban-vision-api-kt/tree/main/.claude/skills/wiki-maintenance
Command: npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill wiki-maintenance-agnaldo4j

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of documentation drift by ensuring that every code change is accompanied by a corresponding update to the project's GitHub wiki, maintaining a single source of truth for architecture and operations.

Core Features & Use Cases

  • Wiki Synchronization: Provides a structured mapping between code changes and specific wiki pages to ensure comprehensive documentation coverage.
  • Standardized Workflow: Enforces a consistent process for editing, committing, and coordinating with maintainers for wiki updates.
  • Use Case: When implementing a new observability feature, use this skill to identify the correct wiki page, validate the required Mermaid diagrams, and prepare the documentation commit for the project maintainer.

Quick Start

Use the wiki-maintenance skill to identify the correct wiki page for the recent changes made to the OpenTelemetry configuration and prepare the documentation update.

Frequently Asked Questions about wiki-maintenance

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

FAQPage Schema
How do I keep GitHub wiki documentation in sync with code changes?

To keep GitHub wiki documentation in sync with code changes, you map specific code modifications to dedicated wiki pages and enforce a strict pull request policy that requires corresponding documentation updates before merging.

What is the best way to automate architecture diagram maintenance in a GitHub wiki?

Architecture diagram maintenance in a GitHub wiki is best handled by validating required Mermaid diagrams during a standardized commit workflow, ensuring technical documentation reflects current structural changes before pull requests are merged.

How does PR-to-wiki synchronization enforce a single source of truth for operations guides?

PR-to-wiki synchronization enforces a single source of truth by blocking code changes unless they are accompanied by matching updates to operational guides and API references within the GitHub wiki repository.

Do I need a dedicated GitHub wiki repository to coordinate documentation updates?

Yes, coordinating documentation updates requires a dedicated GitHub wiki repository to map code changes to specific wiki pages and facilitate a standardized review workflow with project maintainers.

Can I map API references to specific code commits for documentation reviews?

Yes, you can map API references to specific code commits by structuring the documentation workflow to identify the correct wiki page, validate the content, and prepare a documentation commit for maintainer review.

Why does documentation drift occur in project architecture repositories?

Documentation drift occurs because code changes are merged without corresponding updates to architectural documentation, a problem solved by enforcing a strict PR-to-wiki update policy that maintains consistency.