skills.rest
pontscho
pontschoCOMMUNITY
Explore all skills by this author →
GitHub

p:wiki

Maintain a code-verified documentation wiki under docs/ with ingest, lint, query, and adopt operations.

1|Updated Jan 7, 2026
Search Tags:#automation#documentation#governance#anchors#wiki#lint#knowledge-base
One-click install
npx skills add https://github.com/pontscho/prompt-heaven --skill p-wiki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: p:wiki
Source: https://github.com/pontscho/prompt-heaven/tree/main/ClaudeCode/skills/p%3Awiki
Command: npx skills add https://github.com/pontscho/prompt-heaven --skill p-wiki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Build and maintain a persistent, code-verified knowledge base under docs/ so you can keep documentation in sync with code, audit staleness, and answer questions from the repository.

Core Features & Use Cases

  • Centralized docs: a living wiki that evolves with the codebase.
  • Code-anchored verification: every factual claim can be anchored to source symbols.
  • Ingest, lint, query, and adopt workflows: orchestrated by the wiki engine.

Quick Start

Ask the wiki engine to ingest, lint, or query your repo to begin building the docs wiki.

Frequently Asked Questions about p:wiki

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

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

To keep documentation in sync with code, this Skill builds a persistent, code-verified knowledge base under docs/ that anchors factual claims to source symbols and audits for stale references as your codebase evolves.

What is the best way to lint a knowledge base for broken or stale references?▼

Linting a knowledge base for broken references is handled by the wiki engine's delegated janitor, which enforces a frontmatter contract and validates anchor resolution via MCP to audit stale or broken documentation links.

How do I automate documentation governance for my repository?▼

Automating documentation governance involves enforcing a frontmatter contract and using delegated execution for ingest, lint, query, and adopt operations to maintain a centralized, living wiki that evolves with your codebase.

Does the wiki ingest workflow support answering questions directly from the docs?▼

Yes, the wiki ingest workflow supports answering questions directly from the documentation by building a code-anchored knowledge base that can be queried to retrieve verified information from your repository.

What are the limitations of maintaining a code-anchored knowledge base?▼

Maintaining a code-anchored knowledge base requires strict adherence to a frontmatter contract and anchor resolution via MCP, meaning documentation lacking proper frontmatter or source symbol anchors will fail lint audits and cannot be verified.

Related Skills

Explore More Content & Communication Skills→
YuJunZhiXueYuJunZhiXue
596

knowledge-absorber

Convert multi-source content into structured Markdown and HTML teaching notes.

Community
Advanced
clover-stormclover-storm

sync-docs

Detect code changes from git diffs and update corresponding documentation sections.

Community
Intermediate
liangdabiaoliangdabiao
133

llm-wiki

Convert URLs, PDFs, and local files into an interconnected wiki.

Community
Advanced
channgchanng
20

docsify

Generate static documentation websites from markdown files with sidebar navigation.

Community
Basic