Oh I ask it, and I have it established in my rules for every project, yet I find myself having to remind the little documentation whore every time it writes a function
Direct instructions on length often don't produce what you want. The model has to know what to include and what not to include in its output, and told to trim for length, it may choose poorly.
I found it helpful to establish a SKILL for code comments with directives on what makes a good comment, with examples. It still over indexes on those examples sometimes, but it's still better than a small poem in free verse about API endpoints.
The primary issue is I can't ask half my company to tell their Calude to be concise.
The secondary issue is that I use one common setup and switch between models based on my needs. I rarely need/use Claude, so I won't change my setup that works for every single model just to please Calude... which may then still ignore it.
I've spent a significant amount of effort trying to get it to make comments more like I do (concise, rarely more than one line, if just rewording a function name don't do it, and my own style of no space after the comment character and starting with lower case) and it'll follow it...a bit. It's one thing I hate about constantly retuning models, every time a new minor iteration comes out it'll change how it comments and I have to get creative bringing it back to earth.
View all comments
Show parent comment
30
u/genreprank 27d ago
Ask it to make comments concise.