Generate README, AGENTS.md, CONTRIBUTING.md, and per-crate markdown from source inspection.
npx skills add https://github.com/LudwigAJ/swell --skill docs-worker-ludwigaj
Please help me install this Agent Skill. Skill: docs-worker Source: https://github.com/LudwigAJ/swell/tree/main/.factory/skills/docs-worker Command: npx skills add https://github.com/LudwigAJ/swell --skill docs-worker-ludwigaj
This Skill removes the guesswork from writing and updating repository documentation by turning codebase inspection into accurate, consistent markdown for both humans and AI agents.
Ask the docs-worker skill to inspect the repository and draft the required markdown documentation with verified commands, paths, and code references.
High-intent search queries and answers about installing and using this skill.
Generate accurate repository documentation by inspecting source code to draft markdown files with verified commands, paths, and code references. This process cross-checks file paths and type names against the codebase to keep README and onboarding docs grounded in reality.
AGENTS.md is module- or crate-specific guidance for AI agents covering responsibilities, public APIs, testing patterns, and integration points. Create it by inspecting the codebase to produce accurate markdown documentation that defines agent-facing workflows and integration points.
Write per-crate documentation by inspecting source code and validating build commands before drafting markdown. This verification-first writing cross-checks file paths, type names, and build instructions against the actual codebase to ensure crate-level responsibility docs remain accurate.
Yes, you can refresh existing README and CONTRIBUTING files by inspecting the current codebase state and regenerating markdown. The documentation process applies consistency checks across links, type names, and commands to update onboarding guides and usage references accurately.
Keep technical documentation consistent with source code by cross-checking file paths, type names, and commands against the codebase during generation. This verification-first approach ensures markdown documentation for humans and AI agents stays grounded in reality.
Automated documentation generation works for onboarding guides and usage references by inspecting the repository to draft required markdown. It validates commands and code references, ensuring both human- and agent-facing documentation accurately reflects installation workflows and integration points.
C0ntr0lledCha0sMap directory structures, trace imports and data flows, and locate entry points in unfamiliar codebases.
mirkoserticUpdate Megahub README, BLOCKS.md, HUBAPI.md, and LUMP.md documentation.
TheRealSeberGenerate cross-referenced Markdown documentation for Java codebases via static analysis.
pelchersGenerate Markdown project documentation from repository structure and metadata.
