ZeeshanSultan
UserYour AI writes docs faster than anyone can check them. DocGov checks them — catches stale docs, duplicate files, and docs that contradict your code. Claude Code plugin + CLI.
Categories
Indexed Skills (11)
tag
Reorganize existing documentation — add missing frontmatter, split oversized documents, extract overgrown README sections, merge duplicates, and archive superseded documents. Use for "clean up the docs", oversized files, duplicate documents, or after onboarding leaves judgement calls.
publish
Analyze which documentation is safe to publish externally, detect information that would leak, and produce external-lens rewrite briefs. Use before publishing docs, opening a repository, or moving internal documentation to a public site.
setup
Establish DocGov documentation governance in this repository — infer the project mode and layout, create the taxonomy namespaces, install agent documentation rules, and build the initial registry and graph. Use when a repository has no .docgov/config.yaml yet.
brief
Load the minimal authoritative documentation context for a topic or domain before changing code — the constitution, the canonical specification, the invariants in force, the relevant ADRs and the machine contracts, and nothing else. Use before implementing or modifying anything in a governed area.
create
Create a new governed document of the right class in the right place, with its template, its required sections, and its relationships already wired into the documentation graph. Use whenever new documentation is needed — a PRD, TRD, ADR, threat model, runbook, domain spec, guide or README.
inspect
Review documentation quality against its audience lens, find contradictions between documents, and check whether another agent could safely act on a document. Use for "review my docs", documentation quality checks, contradiction hunting, or before publishing.
review
Inventory, classify and produce a migration plan for a repository that already has documentation. Detects duplicates, contradictions, oversized documents, wrong locations, missing frontmatter and coverage gaps, then writes a plan that changes nothing until approved. Use for existing repositories, messy documentation trees, or "organize my docs".
stale
Detect documentation drift — implementation changed but documentation did not, documentation changed but implementation did not, machine contracts ahead of their derived docs, and semantic staleness. Use for "are my docs still true", before a release, or after a large change.
affected
Analyze which documents a code change affects and produce the documentation change manifest — required updates, optional updates, and the PR-ready review comment. Use before committing, when opening a PR, or for "what docs do I need to update".
find
Search documentation with authority-aware ranking, so the canonical specification is returned before the tutorial that paraphrases it. Use for "where is X documented", "what do we say about Y", or finding the authoritative source for a behaviour.
health
Score documentation health across coverage, freshness, consistency, structure, discoverability, cross-linking, canonical integrity and metadata, and list the gaps the repository's own stack implies. Use for "how are my docs doing", documentation audits, or a periodic review.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.