Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By arimxyer
Maintain documentation health with automated quality monitoring, sync workflows, and session journaling via Python hooks that log Claude Code sessions without manual file writes.
npx claudepluginhub arimxyer/doc-manager-mcp --plugin doc-managerComprehensive documentation health dashboard with metrics
Assess documentation quality
Quick documentation health check
Synchronize documentation with code changes
Documentation lifecycle expert and orchestrator. Analyzes documentation state, assesses quality, coordinates sync workflows, and delegates content work to doc-writer. Use for any task requiring documentation analysis, validation, quality assessment, workflow orchestration, or state management. Do NOT use for straightforward content writing tasks.
Documentation content specialist. Creates and updates documentation files with platform-specific formatting, validates own work, and reports results. Use for straightforward content tasks with clear scope - writing API docs, updating guides, creating examples. Do NOT use for workflow orchestration, quality assessment, or state management.
Deep expertise for documentation lifecycle orchestration. Quality assessment frameworks, workflow patterns, delegation protocols, and release checklists. Auto-loads for doc-expert agent.
Documentation lifecycle management skill. Activates when user mentions documentation, docs, sync, quality, validation, releases, or setup. Routes to appropriate agent (doc-expert for orchestration, doc-writer for content) and provides gentle reminders about documentation health.
Deep expertise for documentation content creation. Templates, platform formatting guides, and style principles. Auto-loads for doc-writer agent.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Generate and maintain documentation from code with drift detection. Validates docs against source, auto-generates from code patterns, syncs outdated content, and provides reusable templates for consistent documentation.
Documentation quality validation: broken links, orphan docs, glossary, structure
Documentation and authoring workflow router: audit docs vs code drift, sync docs after changes, optimize prompts and SKILL.md files, validate GLFM and Markdown formatting, summarize files/URLs/images with fidelity enforcement. Use when: docs are out of date, CLAUDE.md needs improving, SKILL.md needs optimizing, checking if documentation matches code, summarizing files or URLs.
Documentation agents — technical writer, documentation architect
Agents specialized in technical documentation and knowledge management. Focuses on documentation architecture and user-focused writing.
Documentation review, cleanup, and generation with AI slop detection, style learning, and human-quality writing enforcement
PixiJS v8 development guide with bundled API references, code patterns, and best practices from official documentation.
Comprehensive documentation lifecycle management powered by an MCP (Model Context Protocol) server. Automates documentation creation, maintenance, quality assessment, and synchronization for software projects.
The doc-management plugin provides an interactive documentation workflow with specialized agents and quick commands, powered by the doc-manager MCP server.
Install:
# Add the marketplace
/plugin marketplace add arimxyer/doc-manager-mcp
# Install the plugin (automatically configures MCP server)
/plugin install doc-manager@doc-manager-suite
What you get:
@doc-expert - Documentation expert who analyzes state and directs next steps@doc-writer - Content specialist who creates/updates docs/doc-status, /doc-sync, /doc-quality - Quick commands for common workflowsExample workflow:
You: "Set up documentation management"
Claude: [Invokes @doc-expert to detect platform and initialize]
You: "/doc-sync"
Claude: [Detects changes, updates docs via @doc-writer, validates, updates baselines]
You: "Check quality before release"
Claude: [Runs quality assessment and shows actionable findings]
See the Claude Code Plugin guide for details.
For using the MCP server without the plugin.
Claude Code:
claude mcp add doc-manager --scope project -- uvx doc-manager-mcp
Claude Desktop:
Add to your claude_desktop_config.json:
{
"mcpServers": {
"doc-manager": {
"command": "uvx",
"args": ["doc-manager-mcp"]
}
}
}
Restart your client. Your AI assistant can then use the 8 doc-manager tools directly.
Other MCP clients:
See Installation Guide for local development setup and alternative installation methods.
With Claude Code plugin:
You: "Set up documentation management for this project"
You: "/doc-sync"
With any MCP client:
Ask your AI assistant to initialize documentation management, check sync status, or validate quality. The AI will use the appropriate tools (docmgr_init, docmgr_sync, etc.) automatically.
See Quick Start Guide for complete workflows and examples.
The doc-manager MCP server provides 8 tools for documentation management:
docmgr_init - Initialize doc-manager for a project (modes: existing, bootstrap)docmgr_detect_changes - Detect code/doc changes (read-only, never writes baselines)docmgr_detect_platform - Auto-detect documentation platform (MkDocs, Sphinx, Hugo, etc.)docmgr_validate_docs - Check for broken links, missing assets, invalid code snippetsdocmgr_assess_quality - Evaluate documentation against 7 quality criteriadocmgr_update_baseline - Update all baselines atomically (repo, symbols, dependencies)docmgr_sync - Orchestrate change detection + validation + quality + baseline updatesdocmgr_migrate - Restructure/migrate documentation with git history preservationSee Tools Reference for complete API documentation.
Doc-manager maintains 3 baseline files in .doc-manager/memory/:
repo-baseline.json - File checksums and metadatasymbol-baseline.json - TreeSitter code symbols (functions, classes, config fields)dependencies.json - Code-to-docs dependency mappingsWorkflow:
1. docmgr_init → Create initial baselines
2. (make code changes)
3. docmgr_detect_changes → Detect changes (read-only)
4. (update documentation)
5. docmgr_update_baseline → Refresh baselines
Or use docmgr_sync mode="resync" to combine steps 3-5.
Example .doc-manager.yml: