
Indexion Wiki
- 4.9k installs
- 1 repo stars
- Updated July 20, 2026
- trkbt10/indexion-skills
indexion-wiki is an agent runbook for creating, updating, indexing, linting, and reconciling indexion project wikis at .indexion/wiki/.
About
The indexion-wiki skill is a runbook for navigating and maintaining indexion wikis stored at .indexion/wiki/ as Markdown governed by wiki.json. Each page requires four synchronized artifacts: page content, manifest entry, search indexes such as vectors.db and tfidf-vocabulary.json, and log.json audit entries. Agents must call wiki pages add or wiki pages update instead of editing .md directly, because direct edits leave search, manifest provenance, and logs stale. Workflows start with wiki index build to read index.md hub pages, detect stale coverage via wiki pages ingest source hashing, fix structure with wiki lint, and catch semantic drift using plan reconcile at the project root until New logical reviews reaches zero. The full maintenance cycle ingests stale tasks, updates pages through the CLI, lints cross-references, reconciles drift, rebuilds navigation, and confirms ingest dry-run reports zero pages needing attention. Commands cover pages plan for greenfield structure, export and import for GitHub wikis, wiki index build --full for vector search, and wiki log audit review.
- Syncs four artifacts per page: .md content, wiki.json, search indexes, and log.json.
- Requires wiki pages update after edits; direct .md changes stale indexes and manifest.
- Detects stale pages via wiki pages ingest hashing sources in wiki.json.
- Runs wiki lint for broken links, orphans, stale sources, and manifest mismatches.
- Uses plan reconcile at project root to track New logical reviews drift convergence.
Indexion Wiki by the numbers
- 4,896 all-time installs (skills.sh)
- Ranked #83 of 1,879 Documentation skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
indexion-wiki capabilities & compatibility
- Capabilities
- four artifact page sync via pages add and pages · source hash stale detection with pages ingest · structural lint for links, orphans, and manifest · semantic drift review via plan reconcile · navigation and vector index builds with wiki ind
- Works with
- github · gitlab
- Use cases
- documentation · planning · orchestration
- Platforms
- macOS · Linux · Windows
- Runs
- Runs locally
What indexion-wiki says it does
A wiki page consists of **four synchronized artifacts**
`wiki pages update` updates all four at once.
Editing the `.md` file directly updates only the first.
npx skills add https://github.com/trkbt10/indexion-skills --skill indexion-wikiAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4.9k |
|---|---|
| repo stars | ★ 1 |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 20, 2026 |
| Repository | trkbt10/indexion-skills ↗ |
How do I maintain an indexion wiki without stale search indexes, manifest drift, or undetected code-doc gaps?
Maintain indexion project wikis with synchronized pages, search indexes, ingest stale detection, lint, and reconcile drift.
Who is it for?
Agents maintaining indexion wikis with ingest, lint, reconcile, and full index rebuild cycles.
Skip if: Skip when the task is only raw text segmentation for RAG without wiki lifecycle management.
When should I use this skill?
User maintains .indexion/wiki, needs stale page detection, wiki lint, plan reconcile, or wiki index builds.
What you get
Synchronized wiki pages, current search indexes, clean lint results, and reconciled documentation drift.
- Updated Markdown wiki pages
- Reconciled wiki.json manifest and search indexes
By the numbers
- Each wiki page synchronizes 4 artifacts: content, manifest entry, search index, and drift metadata
Files
indexion wiki
indexion's wiki system maintains a knowledge base at .indexion/wiki/ as a collection of Markdown files governed by a wiki.json manifest.
A wiki page is not just a .md file
A wiki page consists of four synchronized artifacts:
| Artifact | File | Updated by |
|---|---|---|
| Page content | <id>.md | wiki pages add, wiki pages update |
| Manifest entry | wiki.json | wiki pages add, wiki pages update |
| Search index | vectors.db, search-sections.json, tfidf-vocabulary.json | wiki pages update, wiki index build --full |
| Audit log | log.json | Every wiki-modifying command |
`wiki pages update` updates all four at once. Editing the .md file directly updates only the first. The other three become stale — search returns old results, the manifest carries wrong provenance, and the log has no record of the change.
If you edit a .md directly (e.g. via Edit tool), you must immediately follow up:
indexion wiki pages update \
--id=<page-id> \
--content=.indexion/wiki/<page-id>.md \
--sources="<comma-separated sources from wiki.json>" \
--provenance=synthesized \
--actor="agent:claude" \
--wiki-dir=.indexion/wikiEvery wiki page also carries two provenance fields in the manifest:
provenance:"extracted"|"synthesized"|"manual"last_actor:"indexion"|"agent:<name>"|"user"
Command Structure
indexion wiki
├── pages
│ ├── plan -- propose page structure (init-like)
│ ├── add -- create a new page (writes .md + manifest + index + log)
│ ├── update -- update an existing page (writes .md + manifest + index + log)
│ └── ingest -- detect stale pages by hashing sources
├── index
│ └── build -- rebuild index.md (and optionally vectors.db)
├── lint -- structural integrity checks (no LLM needed)
├── export -- export to GitHub/GitLab wiki format
├── import -- import from GitHub/GitLab wiki format
└── log -- operation audit trailNavigating the Wiki (as an agent)
Before reading individual pages, start with the index:
# Generate or regenerate index.md — the entry point for navigation
indexion wiki index build --wiki-dir=.indexion/wiki
# Then read it
cat .indexion/wiki/index.mdindex.md lists pages by category and identifies hub pages (most-linked pages). Hub pages are the best starting points for understanding an unfamiliar codebase.
Writing a New Page
# 1. Write content to a temp file
cat > /tmp/my-page.md << 'EOF'
# My Page Title
...content...
EOF
# 2. Register it — this writes .md, updates wiki.json, updates search index, appends log
indexion wiki pages add \
--id=my-page \
--title="My Page Title" \
--content=/tmp/my-page.md \
--sources="src/my-module/" \
--provenance=synthesized \
--actor="agent:claude" \
--wiki-dir=.indexion/wikiThe --sources field links the page to source files for change tracking. Always specify it — pages without sources are invisible to wiki pages ingest.
Updating an Existing Page
# 1. Write new content to a temp file
cat > /tmp/updated.md << 'EOF'
# Updated Page
...new content...
EOF
# 2. Update — this overwrites .md, updates wiki.json metadata,
# incrementally updates the search index, and appends to log.json
indexion wiki pages update \
--id=existing-page \
--content=/tmp/updated.md \
--sources="src/my-module/,src/other/" \
--provenance=synthesized \
--actor="agent:claude" \
--wiki-dir=.indexion/wikiExpected output: Updated page 'existing-page' (search index updated)
Detecting What Needs Updating
# Find pages whose source files have changed since the last run
indexion wiki pages ingest --wiki-dir=.indexion/wiki
# Preview without recording the new hash state
indexion wiki pages ingest --dry-run --wiki-dir=.indexion/wikiingest hashes every source file listed in wiki.json and compares against .indexion/wiki/ingest-manifest.json. It outputs an update task list but does not rewrite pages — that is the agent's responsibility.
Workflow: 1. Run wiki pages ingest to get the task list. 2. For each task, read the changed source files. 3. Update the wiki page with wiki pages update. 4. Re-run ingest — it should report 0 pages needing attention.
Verifying Structural Integrity
# Run all 6 structural checks
indexion wiki lint --wiki-dir=.indexion/wiki| Check | What it finds |
|---|---|
| Broken links | wiki://page-id references to pages that don't exist |
| Orphan pages | Pages unreachable from nav tree and not linked by any other page |
| Missing cross-references | Pages sharing source files that don't link to each other |
| Stale sources | sources paths that no longer exist on disk |
| Empty pages | Pages with near-zero content |
| Manifest-file mismatch | wiki.json entries with no .md file (or vice versa) |
After writing new pages, always run wiki lint and fix any issues before finishing.
Cross-reference warnings are common when related concepts are split across pages. Fix them by adding a ## See Also section with wiki://page-id links.
Verifying Content Accuracy (plan reconcile)
wiki lint catches structural problems. plan reconcile catches semantic drift — whether the code symbols described in a wiki page still exist and whether the code has changed since the page was last written.
Always target the project root (`.`). The --doc flag restricts which documents participate, but the target directory determines the code symbol universe. Targeting a subdirectory shrinks the symbol set and produces zero-fragment reports.
indexion plan reconcile \
--doc='.indexion/wiki/*.md' \
--doc-spec=markdown \
--format=md \
.Reading the report
Summary — key metric is New logical reviews (fresh drift since last run).
Suggested Review Groups — the actionable core:
| Category | Meaning | Action |
|---|---|---|
stale_doc | Code changed after the wiki page was last updated | Update the page via wiki pages update |
missing_doc | Code symbols with no matching wiki coverage | Add coverage or create a new page via wiki pages add |
review_both | Wiki is newer than code | Verify the wiki content is correct; this is the expected state after a maintenance cycle |
Each group lists affected symbols and the Docs: wiki pages involved. Groups without a Docs: line mean no wiki page covers that module.
Residual candidates that persist after maintenance
Reconcile candidates never reach zero. Three sources of persistent candidates:
1. Modules without wiki pages produce missing_doc. Create pages if coverage is needed. 2. Qualified method names (Type::method in wiki) don't match bare symbol names (method in code). Verify by grepping the wiki for the symbol name before adding entries. 3. Same-name symbols across modules (get, tokenize, to_json_string) cause cross-module false positives. Check which module the wiki page actually describes.
Track New logical reviews as the convergence metric. When it reaches zero, all actionable drift has been addressed.
Full Wiki Maintenance Cycle
# 1. Detect stale pages (source files changed)
indexion wiki pages ingest --wiki-dir=.indexion/wiki
# 2. Read the index to understand the wiki structure
cat .indexion/wiki/index.md
# 3. For each stale page: read changed sources, write new content to temp file,
# then update through the command (NOT by editing .md directly)
indexion wiki pages update --id=<page-id> --content=/tmp/updated.md \
--sources="..." --provenance=synthesized --actor="agent:<name>" \
--wiki-dir=.indexion/wiki
# 4. Verify structural integrity
indexion wiki lint --wiki-dir=.indexion/wiki
# 5. Verify content accuracy — target project root, iterate until NLR=0
indexion plan reconcile \
--doc='.indexion/wiki/*.md' \
--doc-spec=markdown \
--format=md \
.
# → Fix stale_doc groups first. Re-run. Expect 2-3 rounds.
# → For each fix, use `wiki pages update`, not direct .md edits.
# 6. Regenerate the navigation index
indexion wiki index build --wiki-dir=.indexion/wiki
# 7. Confirm everything is current
indexion wiki pages ingest --dry-run --wiki-dir=.indexion/wikiPlanning a New Wiki from Scratch
When the wiki doesn't exist yet or needs a structural overhaul:
# Analyze the project and generate a page structure proposal
indexion wiki pages plan --format=md <project-dir>
# Then execute the plan: add each proposed page
indexion wiki pages add --id=<id> --title="..." --content=/tmp/page.md \
--sources="..." --provenance=synthesized --actor="agent:<name>"No initialization step is needed. The first wiki pages add call automatically creates .indexion/wiki/ and an empty wiki.json manifest. There is no separate wiki init command.
wiki pages plan uses the CodeGraph to propose concept-based pages, not file-based ones. Prefer concept pages (e.g., "KGF System") over file pages (e.g., "src/kgf/lexer/lexer.mbt").
Building the Search Index
# Build navigation index only (index.md)
indexion wiki index build --wiki-dir=.indexion/wiki
# Build navigation + vector search index (vectors.db)
indexion wiki index build --full --wiki-dir=.indexion/wiki
# Preview index.md without writing
indexion wiki index build --dry-run --wiki-dir=.indexion/wikiWith --full, indexion search .indexion/wiki/ will use the pre-built vectors instead of rebuilding from scratch on each query.
Checking the Audit Trail
# Recent operations
indexion wiki log --wiki-dir=.indexion/wiki --tail=20
# Full log as JSON
indexion wiki log --wiki-dir=.indexion/wiki --jsonEvery pages add, pages update, lint, pages ingest, and index build call appends to .indexion/wiki/log.json. Use the log to verify that previous agent runs completed correctly, or to understand why a page was last modified.
Key Pitfalls
Backtick-quoted `wiki://` references are not links. The lint checker correctly ignores `wiki:// in code spans. Use bare wiki://page-id or Markdown links Title` to create real cross-references.
`wiki pages ingest` manifests state at the time of the last run. If you add new source files to a page's sources list via pages update, the next ingest run will show that page as needing attention (because the new sources have no recorded hash). This is expected behavior — run ingest again after the update to record the baseline.
Related skills
How it compares
Pick indexion-wiki over static docs folders when wiki pages need automated stale detection and code-to-doc reconciliation inside the repository.
FAQ
What does indexion-wiki do?
It documents wiki pages add, update, ingest, lint, reconcile, and index build commands for synchronized knowledge bases.
When should I use indexion-wiki?
When editing project wikis, detecting stale pages, fixing links, or reconciling code symbols against docs.
Is indexion-wiki safe to install?
Review the Security Audits panel on this listing before installing in production.