- Home
- Skills
- Technical Documentation
- Git Wiki Builder: Team Notes to a Linted Wiki
Git Wiki Builder: Team Notes to a Linted Wiki
Nobody keeps a wiki current, and when two documents disagree nobody notices until someone builds the wrong thing.
$1
Works with the AI Agents you already use
Git Wiki Builder: Team Notes to a Linted Wiki
Example session with this skill installed
Build the wiki from the meeting notes and design docs we just committed.
- Read your context and instructions
- Compiled the git wiki builder
$ python3 scripts/preflight.py
mode : git
branch : main HEAD=0323d86 N=3 range=full
build log : WIKI/_meta/build-logs/build_3_0323d86.md
changes : 4
A Source/design/action-items-design.md
A Source/design/realtime-sync-design.md
A Source/meetings/kickoff-2026-10-20.md
A Source/research/search-options.md
$ python3 scripts/lint_source.py
Source Lint passed — 4 document(s) checked in Source/
Ingested → 6 pages
+ WIKI/Domain/product-team-notes-app.md (agreed)
+ WIKI/Topic/realtime-collaborative-editing.md (conflict)
+ WIKI/Topic/action-items-tracking.md (agreed)
+ WIKI/Topic/notes-search.md (agreed)
+ WIKI/Concept/sync-transport-choice.md (conflict)
+ WIKI/Concept/crdt-offline-sync.md (agreed)
~ WIKI/Index.md
$ python3 scripts/verify_wiki.py # attempt 1
== Ingestion Lint FAILED ==
- WIKI/Topic/notes-search.md: tag 'search' not in the closed vocabulary
$ python3 scripts/verify_wiki.py # attempt 2 (tag removed)
Ingestion Lint passed — 6 wiki page(s) checked in WIKI/
Build log — Contradictions
- Sync transport: SSE (commit 3, 2026-10-20, Source/meetings/kickoff-2026-10-20.md)
↔ WebSocket (commit 3, 2026-10-23, Source/design/realtime-sync-design.md).
Pages set to `conflict`.
Build log — Insights
- The WebSocket design lists proxy blocking as its main risk — the same reason
the kickoff picked SSE. A fallback transport would satisfy both.
- Offline is a product requirement, but v1 search is server-side PostgreSQL:
search will not work offline.
$ python3 scripts/record_build.py
[gitwiki] recorded build in WIKI/_meta/state.json: 0323d86838bbe3eb39cdc274eaf54ac58ed3cc87
Ready to commit (auto_commit is off):
git add WIKI && git commit -m "wiki: build commit 3 (0323d86)"
Next: the team needs to agree on the sync transport in Source/.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Team knowledge is scattered across meeting notes, design docs and research memos. Nobody keeps a wiki current, and when two documents disagree nobody notices until someone builds the wrong thing.
What it does
Humans write in Source/. The skill maintains WIKI/. A companion skill turns the wiki into specs in SPEC/.
- Source Lint: checks human docs (frontmatter, ASCII names, date format, obvious secrets). If it fails, the build stops and the agent never edits your docs to make it pass.
- Change detection: only Source docs changed since the last ingested commit (falls back to file hashes in non-git folders).
- Ingest: extends existing pages first, then creates Domain / Topic / Concept pages by how big the idea is. Never one page per file.
- Contradictions: both positions are recorded, the page is set to
conflict, and each side's commit, date and path is logged. The agent never decides for the team. - Ingestion Lint: tier ≠ folder, status/tag vocabularies, dates, missing sources, broken
[[links]], orphans, Index completeness. The agent fixes its own output, at most 3 tries. - Build log +
hot.mdsnapshot + state, then commits (asks first unlessauto_commitis on). Never pushes.
Status lifecycle
agreed · in-review (agent gap-filling) · conflict · deprecated (never deleted).
Configurable
.gitwiki.json: folder names, closed tag vocabulary, en/ko frontmatter keys, branch guard, auto-commit, commit prefix. init_gitwiki.py scaffolds everything and never overwrites.
Bundled
6 stdlib-only Python scripts (init, preflight, lint_source, verify_wiki, record_build, shared helpers) plus the full contract reference.
Works with Git Wiki Ask (cited Q&A) and Git Wiki Spec Builder (commit-pinned specs).
Inspired by Andrej Karpathy's "LLM Wiki" pattern and the MIT-licensed claude-obsidian project. Original implementation.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Commit-based: uncommitted Source edits are ignored until committed (preflight warns). Frontmatter parser is a small YAML subset (no multi-line values). Only [[wikilinks]] are link-checked. The linters guarantee structure, not meaning; wiki quality depends on the agent model. No git hooks; trigger it manually or from your own CI.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 22 days ago
- Software
Python 3
Git
Permissions
File Scopes
Never edits Source docs; no network; never pushes; subprocess is used only for git; local commits only with approval.