Doc files nobody asked for, and READMEs that grow by 40 or more lines nobody asked for
Comments and text: one of the ways AI coding agents bloat software, from lessloc's pattern catalog. lessloc catches it as unrequested-doc.
What makes doc files and README growth nobody asked for a bad practice?
The standard that calls it a bad practice: YAGNI.
What does lessloc do about doc files and README growth nobody asked for?
lessloc catches it as unrequested-doc.
unrequested-doc(tier 3): A doc file nobody asked for, or a doc that grew by 40 or more lines without a request for docs.
Related patterns
The other patterns in Comments and text:
- Comments that narrate what the code does: lessloc catches it as
narration. - Banners, dividers, closing-brace comments, emoji decoration: lessloc catches it as
narration. - Docs that restate the name: lessloc catches it as
narration. - History and messages to the requester: lessloc catches it as
history. - Comment blocks and comment-heavy changes: lessloc catches it as
comment-blockandcomment-density. - Log lines that narrate each step: lessloc catches it as
narration(three or more in a file). - Docs that still name what a change removed: lessloc catches it as
stale-doc. - Summary, report and notes files: lessloc catches it as
junk-fileand refuses it before it lands. - Docs deleted wholesale to shrink a change: lessloc catches it as
doc-removed. - Always-loaded instructions that grow: lessloc catches it as
long-instructions. - Commit messages that recap the diff file by file: The commit hook warns when a message lists the files the diff shows.

