My coworkers continue to dump hundreds of lines of AI documentation in every PR and every other line of code has between one and ten lines of AI generated comments, talking about the real unlock and how things are byte for byte identical on the load bearing path or how the acceptance ladder is misleading.

Features are coming out and metrics are improving, but we’re basically in a post readability code base, with the occasional performative comment about a variable name.

I don’t really know how to address this situation or if it needs addressed. I certainly don’t read the long-winded AI comments or the AI documentation, but perhaps it’s useful for the AI on its next pass.

Have you considered talking about it? You're in a professional environment collectively working in a new way with a group of people. It's up to somebody to have opinions about what does and doesn't suck. If you silently go along and don't say anything you're dooming yourself and all of us to a lifetime of this garbage.

My "favorite" Claudism is when I critique its work and ask it to remove some unnecessary part of the design -- and then the diff has more green than red because it added comments about why the code is no longer there -- the code that was never in the mainline and never asked for!

My team uses a Claude Code hook that blocks any comment more than 2 lines long, and when tripped it encourages the agent to rewrite the comment more concisely and focus only on the "why" not the "what" of the code. I've found this extremely useful for code reviews.

I have five enforcement mechanisms: 1000 line max edit, PR comment character limits (get to the point of your description), ISO 24495 conformance check, and enforced code line citation that must exist, be a function declaration for the start of all paragraphs and inline commentary must be three lines or less and inline comments contribute max 10% of the PR. Fail any of these, automatic PR denial with no human intervention.

Congratulations: now only AI can iterate on your codebase!

Prune the comments? Instruct the LLM to print less comments (this one is genuinely hard though). What's really happening is that you don't have a strong enough review process (or a code standards process) to offset this. The one issue I see with this is that your team is almost certainly _NOT_ doing any kind of code review (especially if they're leaving comments like that). The other problem is that excessive comments actually harm LLM output, I've done tons of A/B testing, and pruning comments actually helps LLMs spot bugs, among other things.

I dump AI output in PRs, because it ads context for the AI reviewer.

Honestly, if you saved a ton of hours with the model coding for you, at least give me 30 minutes of your own words, show me you know what you're shipping, if you can't do that, then I don't know if I want to approve the PR. My first job we always did peer review in a meeting room when a PR looked a little too much, you can't exactly bring in GPT into a meeting so its a good time to ask simple questions about the change to ensure you understand it just as much as they do.

You forgot the smoke tests that passed.

Am I the only one who's had Claude almost systematically remove human-written comments?

It might be touching one line of actual code in a file, and take advantage of it to remove 20+ lines of actual useful comments.

Everybody is talking about the opposite, so I'm wondering if this is rare.

It's a code review, right?

Give feedback that about the docs and block merging till the issue is resolved.

Just wait until you see vibe contracts, vibe requirements and vibe legal documents

I address it with AI.

Write REVIEW.md.

I have CC check itself pretty well.

I also put into agent/claude/review instructions to write using simple English skill and humanizer skill. Then not to write redundant comments.

It’s not perfect but definitely catches lots of slop.

> perhaps it’s useful for the AI on its next pass

Yes, that's the entire point. And it is extremely useful. Why wouldn't I want this?