What problem does it solve? Repositories often ship with missing, stale, or inconsistent root documentation, and drafting READMEs or license text from scratch leads to invented details and mismatched tone. This Skill detects the repo's tone and file needs, confirms them with the user in one batched question, and writes or patches documentation grounded in the actual code. ## Core Features & Use Cases - Tone and disposition detection: Classifies the repo as professional, community, personal, or friendly, and recommends which root files (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT) apply, confirmed via a single batched question. - Gap-based README refresh: Treats existing docs as a checklist, patching stale facts like new env vars or dead links without restructuring content the user didn't ask to change. - Verbatim license copying: Copies canonical license texts (MIT, Apache-2.0, BSD-3-Clause, ISC, Unlicense) from bundled templates, filling only year and holder placeholders instead of generating legal text from memory. - Use Case: Before publishing a side project to GitHub, run this Skill to get a right-sized README, an MIT LICENSE with the correct copyright holder, and a clear recommendation on whether CONTRIBUTING or CODE_OF_CONDUCT files are warranted. ## Quick Start Use the generate-docs skill to create or refresh the README and other root documentation for this repository before publishing it.
