skills.rest
bordenet
bordenetCOMMUNITY
Explore all skills by this author →
GitHub

wiki-verify

Verify wiki page claims such as: version numbers, repository references, file paths, and configuration values by comparing them against live code and package metadata, with optional interactive, report-only, or auto-fix modes.

8|1|Updated Jan 24, 2026
Search Tags:#automation#documentation#codebase#verification#wiki#facts
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill wiki-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-verify
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/wiki/wiki-verify
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill wiki-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation frequently becomes outdated when code, versions, or configurations change, leading to misinformation and wasted time.

Core Features & Use Cases

  • Source Discovery: Detects verification sources from wiki tail sections or a central registry.
  • Claim Verification: Compares version numbers, repository references, file paths, and configuration values against live code.
  • Modes: Interactive prompts, report‑only diff output, or automatic fixing.
  • Integration: Works with the wiki‑orchestrator pipeline and can be triggered before publishing or during periodic audits.

Quick Start

Ask wiki-verify to scan the current documentation page, highlight any stale claims, and apply fixes automatically.

Frequently Asked Questions about wiki-verify

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

FAQPage Schema
How do I verify wiki documentation against a codebase to find stale information?▼

You can verify wiki documentation by comparing claims like version numbers, repository references, and configuration values against live codebase sources to eliminate stale information automatically.

What is the best way to automate keeping wiki pages accurate when code changes?▼

The best way to automate wiki accuracy is scanning documentation pages to detect verification sources, comparing claims against live code, and applying fixes automatically before publishing or during periodic audits.

Can I generate a report of outdated wiki facts without modifying the page?▼

Yes, you can generate a report of outdated wiki facts using report-only diff output mode, which highlights stale claims without applying automatic fixes to the documentation.

Does wiki verification require access to source repositories and wiki APIs?▼

Yes, wiki verification requires access to the wiki API and source repositories to parse and compare documentation claims with live file contents and package metadata accurately.

How do I automatically fix incorrect configuration values in documentation?▼

You can automatically fix incorrect configuration values in documentation by applying auto-fix mode to scan pages, detect stale claims, and update values directly against authoritative codebase sources.

When should I use an interactive wiki verification mode instead of auto-fix?▼

Use interactive wiki verification mode instead of auto-fix when you want to manually review detected stale claims and approve changes before applying fixes to the documentation.

Related Skills

Explore More Content & Communication Skills→
apexradiusapexradius

onboard-dev

Automate developer onboarding by scanning repository metadata and mapping codebase architecture.

Official
Advanced
bordenetbordenet
8

wiki-orchestrator

Run a quality pipeline for bulk multi-page wiki updates.

Community
Advanced
tranvietanh0tranvietanh0

gk:wiki

Create, update, and audit game design wiki pages against the codebase.

Community
Intermediate
quangphu1912quangphu1912
1

tracing-dependencies

Detects circular dependencies, architectural violations, and conflicts in module graphs via static code analysis.

Community
Advanced