Git Wiki Pack: Builder, Spec Builder and Ask

    1

    All three Git Wiki skills in one pack: turn committed team notes into a linted wiki, write commit-pinned specs from it, and get cited answers. About 25% less than buying separately.

    $2

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Git Wiki Pack: Builder, Spec Builder and Ask

    Example session with this skill installed

    Build the wiki from the notes we just committed, then write the spec.

    • Read your context and instructions
    • Compiled the git wiki

    Demo: the result (real run, trimmed):

    $ 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

    What's inside

    All three Git Wiki skills in one pack, about 25% less than buying them separately:

    • Git Wiki Builder turns the team notes committed under Source/ into a linted, cross-linked WIKI/. It runs incrementally per git commit and tracks contradictions instead of hiding them.
    • Git Wiki Spec Builder writes a commit-pinned product spec in SPEC/ from the wiki only. Gaps are marked "Undecided" and conflicts go to Open questions.
    • Git Wiki Ask answers questions strictly from the wiki, cites a page on every claim, and flags anything not yet agreed. It is read-only.

    How they fit together

    Commit notes, then run Builder to update the wiki. Use Ask for cited answers and Spec Builder for a spec your coding agent can implement.

    Requirements

    An agent with file and shell access (Claude Code, Codex, or similar). Python 3.9+ standard library only. git is recommended. No network access, and nothing is ever pushed.

    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 change detection ignores uncommitted edits. Refuses to fill information gaps, marking them 'Undecided'. Verification scripts check structure and links, not prose quality.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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 17 days ago

    Software
    python3 (3.9+)git (recommended)

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables

    No network; never pushes. Env vars GITWIKI_ROOT / GITWIKI_CONFIG are optional.

    Listed17 days ago
    Updated7 days ago

    What's inside

    Frequently Asked Questions

    The skill bridges the gap between messy brainstorming and code implementation by enforcing a three-tier structure (Source, Wiki, and Spec). It solves the problem of AI hallucinations by strictly citing consolidated project truth and marking missing information as 'Undecided' rather than guessing.

    This package is designed to work with Python-based agentic workflows and is optimized for architectures like Claude Code and Codex sub-agents. It uses standard Git and Markdown, making it compatible with any tool that can execute shell commands and read file directories.

    You receive the complete documentation pipeline including the Wiki Ingestion engine, the Contradiction Tracking module, and the Spec Generation tool. It also includes the 'Read-only Responder' sub-agent configuration for querying your project state safely.

    Setup is straightforward for any developer environment running Python 3.9+; you simply point the tool to your project's Git repository. The skill relies on your existing Git history to track changes, so no external database or complex infrastructure is required.

    Unlike generic prompts, this skill enforces a 'strict contract' where every output must be grounded in your documentation. It detects conflicting design decisions and flags them as 'Conflicts' rather than ignoring them, ensuring your coding agent never builds based on outdated or contradictory notes.

    The skill uses a commit-based build system, meaning it primarily processes changes that have been saved to your version control. This ensures a stable 'project truth' and allows you to roll back documentation or see exactly when a specific requirement was introduced.

    New in Technical Documentation