Use when mapping source code files to their documentation counterparts — find which docs cover which code, detect gaps, and resolve doc-to-code relationships.
From docs-guardiannpx claudepluginhub xiaolai/claude-plugin-marketplace --plugin docs-guardianThis skill uses the workspace's default tool permissions.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
A mapping is a pair: (source_file, doc_file). The audit pipeline resolves all mappings before dispatching to agents. Four strategies are applied in priority order.
User-defined mappings in .claude/docs-guardian/config.json:
{
"mappings": [
{ "source": "src/auth/**/*.ts", "doc": "docs/api/auth.md" },
{ "source": "src/db/models/*.py", "doc": "docs/models/${name}.md" }
]
}
The ${name} placeholder expands to the source file's basename without extension.
Glob patterns are supported in source. The doc field can be a literal path or use ${name}.
Each framework adapter knows its own mapping convention:
| Framework | Convention |
|---|---|
| MkDocs | mkdocs.yml nav entries → doc paths under docs_dir |
| VitePress | .vitepress/config sidebar entries → doc paths |
| Docusaurus | sidebars.js entries → doc paths under docs/ |
| Sphinx | toctree directives → .rst files under source/ |
| Plain Markdown | Convention-based (see Strategy 3) |
When no config or framework mapping exists, use naming conventions:
| Source Path | Doc Path |
|---|---|
src/foo/bar.ts | docs/foo/bar.md |
src/foo/bar.ts | docs/api/foo/bar.md |
lib/foo.py | docs/foo.md |
pkg/foo/bar.go | docs/foo/bar.md |
src/foo/mod.rs | docs/foo.md |
Try each candidate in order. First existing file wins.
If no doc file exists for a source file, record it as unmapped (potential coverage gap).
Some symbols are documented inline (docstrings, JSDoc, godoc comments) rather than in separate doc files. When a source file has no external doc mapping but contains inline documentation:
INFO that docs are inline-only (not necessarily a problem)MEDIUM coverage gapReturn an array of resolved mappings:
[
{
"source": "src/auth/login.ts",
"doc": "docs/api/auth.md",
"strategy": "config",
"confidence": "high"
},
{
"source": "src/utils/hash.ts",
"doc": null,
"strategy": "unmapped",
"confidence": "none"
}
]