Compare documentation workflows for READMEs, architecture, APIs, onboarding, and maintainable code-linked handoffs.
The job
IncludedREADME and onboarding documentation · architecture or module documentation · maintainer and API documentation
Not this pagemarketing copy · greenfield system design · documentation hosting setup
30-second route
It explicitly supports brownfield build/review work, documentation-surface inventory, compatibility with current IA, and validation handoff.
Editorial confidence: highIts four phases directly cover reconnaissance, architecture mapping, convention detection, and onboarding artifacts.
Editorial confidence: highIt explicitly produces a bounded multi-file wiki with diagrams and verification steps.
Editorial confidence: highThe source says in-repository output occurs only when explicitly requested.
Editorial confidence: highBefore you install
Each directly performs a distinct, source-supported documentation workflow for an existing repository, and their supplied content hashes differ. Use the route that matches the desired deliverable and output location.
Read the intervention guide →Source-led comparison
Facts are extracted from each selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.
Source notes
Why these candidatesEach candidate comes from tracked public sources and has a source-attributed adoption signal. This is a shortlist, not a catalogue or global ranking.
What this cannot establishWe read declared instructions and public signals. We do not run skills, benchmark outputs, audit security, or claim a universal best choice.
Use it forBroad brownfield documentation work spanning repository docs, governance files, reviews, and maintainable handoff notes.
Avoid ifYou only need a narrowly scoped, guided onboarding artifact or a standalone wiki.
ActionInstall and use for build or review documentation work across an existing repository.
EditsInventory current documentation and instruction surfaces first; preserve the existing docs IA and define multilingual parity where relevant.
SetupProvide the desired audience, file/diff scope, framework constraints, investigation depth, and remediation mode.
ContextSupports build/review classification and brownfield mode, with documentation-surface coverage and validation notes.
OutputUpdated documentation or review findings, validation notes, coverage map, governance alignment, and remaining gaps.
ControlStructured workflow with optional bounded sub-agent discovery and synthesis for large repositories.
InvocationNot yet mapped from the source.
Install scopeNot yet mapped from the source.
Agent fitStrong default for comprehensive, maintainable repository documentation.
Watch outIts scope includes governance and agent-instruction files, so specify a narrower file scope when those surfaces are out of scope.
Explicitly targets creating or overhauling documentation in an existing codebase and full-repository documentation audits.SKILL.md:lines 17-25 · inspected 2026-07-20 · high confidence
Its workflow inventories documentation surfaces, preserves current IA in brownfield mode, and returns validation and gap notes.SKILL.md:lines 29-43 · inspected 2026-07-20 · high confidence
Use it forA concise, evidence-led onboarding guide and starter or updated CLAUDE.md for an unfamiliar existing repository.
Avoid ifYou need a full documentation audit, API reference set, or multi-module wiki.
ActionInstall and run the four-phase reconnaissance-to-onboarding workflow.
EditsGenerate or enhance the existing CLAUDE.md rather than replacing it; retain detected repository conventions and mark uncertainties.
SetupPoint it at the repository and request either the full onboarding guide plus CLAUDE.md or only the CLAUDE.md output.
ContextStarts with package, framework, entry-point, structure, configuration, and test discovery, then maps architecture and conventions.
OutputStructured onboarding guide with architecture, entry points, directory map, request lifecycle, conventions, common tasks, plus a project CLAUDE.md.
ControlFour-phase reconnaissance, architecture mapping, convention detection, and artifact generation.
InvocationNot yet mapped from the source.
Install scopeNot yet mapped from the source.
Agent fitBest focused choice for maintainers or contributors getting oriented quickly.
Watch outThe supplied workflow is written in Chinese; choose it when that source language and its focused onboarding deliverables suit the team.
The skill is for systematically analyzing an unfamiliar codebase and generating a structured onboarding guide.SKILL.md:lines 7-17 · inspected 2026-07-20 · high confidence
It maps technology, architecture, key directories, and request data flow after reconnaissance.SKILL.md:lines 50-89 · inspected 2026-07-20 · high confidence
It produces an onboarding guide and a starter or enhanced CLAUDE.md while preserving existing project-specific instructions.SKILL.md:lines 114-179 · inspected 2026-07-20 · high confidence
Use it forA stable, repository-grounded reference wiki with architecture, module deep-dives, onboarding, API coverage where applicable, and Mermaid diagrams.
Avoid ifYou need strategic rationale documentation or want documentation written into the repository without explicitly requesting that location.
ActionInstall and use to generate a bounded wiki from the target repository.
EditsFor large repositories, confirm the selected module list; explicitly request docs/wiki output if the wiki belongs in the repository.
SetupRun from the target repository root; git is required for SHA tracking, while pygount is optional.
ContextDefaults to an external wiki directory, caps the initial pass at 8–10 modules, and supports incremental-update checks through a state file.
OutputREADME, architecture document, per-module docs, class and sequence Mermaid diagrams, getting-started guide, optional API doc, and state file.
ControlRepository scan followed by bounded module selection, grounded writing, and output verification.
InvocationNot yet mapped from the source.
Install scopeNot yet mapped from the source.
Agent fitBest specialist option when the handoff should be a navigable reference wiki rather than general documentation maintenance.
Watch outThe default output is outside the repository; it writes to docs/wiki only on explicit request.
Explicitly generates a comprehensive codebase wiki with architecture, module deep-dives, Mermaid diagrams, and reference documentation.SKILL.md:lines 14-18 · inspected 2026-07-20 · high confidence
The documented procedure produces overview, architecture, module docs, diagrams, getting-started material, and optional API documentation.SKILL.md:lines 43-58 · inspected 2026-07-20 · high confidence
It defaults outside the repository and only writes to docs/wiki when the user explicitly requests it.SKILL.md:lines 33-41 · inspected 2026-07-20 · high confidence
Linux, macOS, and Windows are declared platforms.SKILL.md:lines 1-11 · inspected 2026-07-20 · high confidence
Still comparing?