Blog post announcing pnpm 12 is hard to read, it's AI generated

[sxflynn]

I was excited about pnpm 12 and started to read the blog post here https://pnpm.io/blog/releases/12.0

I could tell very quickly that it was generated by Claude. I find it very hard to actually read.

Please do not allow AI to write your blog posts for you. Just have a human write it, like it has always been.

[zkochan]

This is basically a changelog, not a promotional piece. If you check the other blog posts about released versions, they are in a similar style. They are generated from individual changeset files that are created in every PR to pnpm. If you have specific things that could be improved in this changelog entries, feel free to elaborate. "generated by Claude" and "hard to actually read" is too vague. I personally wouldn't read the whole changelog just the sections that I am interested in.

Sure, I would have written the block post differently if I wanted to share it on other platforms and get more traffic. However, I felt like at this point a "rust rewrite" became a very boring topic and overhyped by some competitors.

[sxflynn]

I do apologize for the vagueness. AI generated text is something where you know it when you see it, given how frequently we all use Claude tools at work.

If you want to keep an AI workflow, I think this could be solved by improved prompting. Ask it to not be extremely verbose and include all sorts of tiny little details that don't belong in a chaneglog. I've also had a lot of good luck using the /unslop skill published by a React maintainer. https://github.com/cursor/plugins/blob/main/pstack/skills/unslop/SKILL.md

I always tell Claude to use that skill when composing .md files. Just some ideas to maybe help a bit.

[zkochan]

ok, we can try this

[zkochan]

I see a link to the blogpost was shared in js weekly. Honestly, I have probably underrated how much attention pnpm has.

[zkochan]

done