agentleFS
Sign inStart free
bordenetbordenet/superpowers-plus/skills/wiki/wiki-verify/skill.md

wiki-verify

Skill8 starsChanged 7 months agoMITView on GitHub

Use when wiki pages reference codebase details (versions, repos, configs) that may drift. Verifies claims against authoritative sources and auto-applies fixes by default.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When asked to verify that a wiki page's version numbers, file paths, or config values match the current codebase

    line 32
  2. Very specific:

    Default / --fix: write corrected body to page.md, re-run Stage 5.5 (node tools/wiki-markdown-validate.js page.md), then tools/wiki-write.sh …

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

wiki-verify

Detect stale codebase claims (version numbers, repo names, file paths, config values) in wiki pages. Wrong skill? Links → link-verification · Secrets → wiki-secret-audit · Fact-check decisions/dates → wiki-debunker · Edit pipeline → wiki-orchestrator.

When to Use

  • When asked to verify that a wiki page's version numbers, file paths, or config values match the current codebase
  • Triggered by: verify this wiki page, check if wiki is up to date, validate wiki accuracy, audit the wiki, is this documentation stale
  • Wrong skill? Links → link-verification · Secrets → wiki-secret-audit · Fact-check decisions → wiki-debunker

Modes

ModeFlagBehavior
Fix(default)Auto-apply all fixes (Haiku-safe)
Interactive--interactivePrompt before each fix
Report--reportOutput diff only, no writes

Procedure

1 — Fetch page

tools/wiki-read.sh get "$PAGE_ID" > page.json
jq -r '.text' page.json > page.md

2 — Discover verification sources (tail block or registry)

## 🔍 Verification Sources
<!-- wiki-verify:sources
repos: [backend-service, settings-service]
files: [backend-service/package.json#dependencies]
-->

Fallback: superpowers-plus/wiki-sources.yaml entry keyed by page id. Neither present → STOP: "no verification sources configured."

3 — Classify each claim

Claim typeSourcePass if
Version vX.Y.Zpackage.json / requirements.txtexact match
Repo namegit ls-remote / adapterrepo exists
File pathgit cat-file -e HEAD:<path>exit 0
Import / vendorgrep -r <name> src/any hit
Config valuetarget config fileexact match
PR / commit refgh api, git logreference resolves
Date claimgit log --after/--beforecommit exists

Mark each: ✅ CURRENT · ⚠️ STALE · ❌ WRONG · ❓ UNVERIFIABLE.

4 — Apply fixes (mode-dependent)

  • Default / --fix: write corrected body to page.md, re-run Stage 5.5 (node tools/wiki-markdown-validate.js page.md), then tools/wiki-write.sh update --doc "$PAGE_ID" --content page.md.
  • --interactive: prompt [U]pdate / [S]kip / [A]ll / [Q]uit per finding.
  • --report: emit diff to stdout, exit 0.

5 — Maintenance footer (required after any write)

Page MUST end with *🔄 AI-maintained — invoke wiki-verify skill to update* placed after ## 🔍 Verification Sources. Omit dates and URLs.

Authoritative sources

git show/log · repo adapter · package.json · requirements.txt · YAML/JSON/TOML config · .env.example. Registry fallback: superpowers-plus/wiki-sources.yaml.

Failure modes

FailureFix
Source itself staleCross-reference ≥2 sources (repo + API)
UNVERIFIABLE left silentFlag with citation-needed tag
False STALE on pinned versionRespect lock-file / pinned: annotations
wiki-write.sh exit 1STOP; ask user; do not retry

Background, mode rationale, authoritative-source ordering: rationale.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free