chore: Enforce Minimal Code Comments - #2630
Conversation
🎩 PreviewA preview build has been created at: |
morgan-wowk
left a comment
There was a problem hiding this comment.
🤖 Agent review. Verified no functional directive comments were removed anywhere (no eslint-disable/@ts-*/pragmas/etc.), the one doc value change (MIN_DOCKED_HEIGHT 100→50 in WINDOWS.md) is a correct fix vs the actual constant, and the branch passes pnpm run lint. One cross-PR concern (inline).
7e0d865 to
96425ae
Compare
|
^ inline concern has been addressed |
96425ae to
360fae0
Compare
morgan-wowk
left a comment
There was a problem hiding this comment.
🤖 Agent-assisted re-review (posted by Morgan). Approving. local/no-type-member-comments is now warn rather than error, which resolves the concern: in-flight branches that still carry an interface/object-type comment will surface a lint warning on rebase instead of a hard CI failure, so nobody gets a silent red build from a merge they didn't touch. Flipping to error later once the tree is clean is an easy follow-up. (The minor 'rename the field' message not quite fitting inline TSTypeLiteral cases is cosmetic — fine to leave.)
360fae0 to
8f4b718
Compare

Description
Claude has been bloating our codebase with spammy code comments for far too long. This PR aims to reign in the AI and assert dominance!
Hopefully after this we will get much less long-winded and pointless code comments. Updated directives to the AI aim to remove the JSDoc standard and reduce self-explanatory code comments. The PR also does an initial high-level sweep and cleans up a few places as a proof of concept.
This should make our code more concise and readable in the long term.
Related Issue and Pull requests
Type of Change
Checklist
Screenshots (if applicable)
Test Instructions
Additional Comments