mcpax

Maintain project documentation by extracting specifications from test cases and implementation code. Creates or updates README, CLI usage guides, TUI guides, and API references using tests as the source of truth. Use this skill when the user asks to update docs, check if docs are outdated, write documentation for a feature, generate a usage guide, or sync docs with code. Also trigger for phrases like "ドキュメントを更新して", "READMEが古くなってないか", "この機能の ドキュメントを書いて", "docsを最新にして", "使い方を書いて", "doc maintenance", "sync documentation", "generate docs from tests". This skill should also be considered when preparing a PR that changes CLI commands, TUI screens, or public APIs — documentation may need updating alongside the code.

Audit test coverage as living specification by comparing implementation against test cases. Detects specification gaps (public APIs without tests), contradictions (tests asserting behavior that differs from implementation), stale tests (testing removed/changed code), and missing edge cases. Use this skill when the user asks to check test coverage, verify spec coverage, audit tests, find contradictions between tests and code, or ensure tests serve as reliable specification. Also trigger for phrases like "are my tests up to date", "do tests match the implementation", "spec coverage", "test audit", "仕様カバレッジ", "テストと実装の矛盾", "テストの網羅性". Supports scoped checks (e.g., "check CLI spec coverage", "audit TUI tests") as well as full-project audits.