Resolve documentation ownership, edit roots, checks, and human handoffs before an agent edits code.
The MCP server io.github.AgentsKit-io/doc-bridge resolves documentation ownership and related edit responsibility before an agent changes code. It helps determine edit roots, applies checks, and supports human handoffs to complete documentation updates with appropriate review.
🛠️ Key Features
Resolve documentation ownership
Determine edit roots prior to edits
Perform checks before an agent edits code
Coordinate human handoffs
🚀 Use Cases
Ensure the correct party owns a documentation change
Route documentation edits from the right edit root
Add validation steps before code/doc modifications
Integrate human review into an agent-driven workflow
⚡ Developer Benefits
Reduces ambiguity about who should edit documentation
Adds pre-edit checks and structured handoff points
Supports safer agent edits by establishing ownership and scope first
⚠️ Limitations
No additional details on tool count, supported protocols, or specific interfaces were provided in the source data.
Turn your docs into executable handoffs for coding agents.
doc-bridge reads your repo docs, ownership map, and human documentation site, then gives every agent the same answer:
where to start reading
which files/packages it may edit
which checks prove the change
which human docs explain the feature
It is not a wiki or hosted RAG. The core works without any LLM or API key; the documentation portal dogfoods AgentsKit Chat as an optional surface over that deterministic layer.
doc-bridge maps human docs into structured agent handoffs
Why teams use it
Agents are powerful, but most repo docs are written for humans. The result is familiar: the agent guesses ownership, edits the sibling package, runs the wrong test, or ignores the human guide that already explained the rule.
doc-bridge works in both directions:
doc-bridge connects human docs to coding agents and agent memory back to draft docs
Direction
What it does
Command
Human docs → agents
Turns Fumadocs, Docusaurus, markdown, and ownership docs into AgentHandoff
ak-docs index · ak-docs query --agent
Agent memory → docs
Reads .agent-memory/** and .cursor/rules/*.mdc, classifies what should become project docs, and drafts a human-reviewed promotion
That contract works from the terminal, MCP, CI, and optional RAG/chat.
60-second proof
bash
npm i -D @agentskit/doc-bridge
npx ak-docs demo --text
No config, no docs to read first. Output shows before/after, a real handoff, gate red→green, and the MCP snippet:
code
After (handoff.resolve / query --agent)
✓ target: auth (packages/auth)
✓ start: docs/for-agents/packages/auth.md
✓ edit: packages/auth
✓ checks: pnpm --filter @demo/auth test · pnpm --filter @demo/auth lint
✓ human guide: /docs/guides/auth
Gate: red → green
Monorepo fixture with auth + billing:
bash
npx ak-docs demo --fixture monorepo --text
Verify the real handoff path
This checked example runs the bundled demo through the public CLI. The README gate compares this block byte-for-byte with the executable fixture and runs it on every PR.
The Action checks the committed index before changing anything, pins the matching npm package, and rejects non-exact package versions. See the Marketplace guide.
Run ak-docs doctor --badge locally to refresh — or pnpm coverage:badge in CI.
Or locally:
bash
ak-docs index && ak-docs gate run
Gate fails with Index is stale. Run: ak-docs index — same check in CI annotations.
Product surface
Core — always (no LLM)
Surface
Purpose
Demo
ak-docs demo — bundled fixture, no setup
Doctor
Coverage score, missing humanDoc/agent doc, next actions
v1.2.1 stable — deterministic Documentation Standard v1 conformance, verified release provenance, Fumadocs portal, Marketplace Action, doctor + CI + skill, and full Tier A/B/C.
bash
pnpm install && pnpm build && pnpm test
pnpm smoke:ollama # optional — skips if Ollama/peers unavailable
