First Open-Source PR

> Run /edit to surface documentation typos automatically

Some missing points: (Ignoring that some project don't like PR written by AI.)

* Manually review carefully that the proposed changes are correct.

* If the PR is too long, split it in parts that make sense. For example:

- fixing all the typos in a file or directory instead of the same project.

- fixing a misspelled word like "bamana" that appears like 5 times in random places

* Write a short comment in the PR. Don't ask the AI to write a 10 pages long PR that includes a AI rant about the importance of bananas in the diet in some countries.

Open Source has a...sigma of lack of quality documentation, encouraging presumably first-time contributors to just use Claude to get a PR isn't actually helping as much as it appears to be. As someone who deals with piles of AI slop submitted by junior sysadmins and devs, the amount of crap I reject is astounding and they always cite posts such as this that encourage this sort of development. Drive-by-developers is what I call them, as they are not invested in the project, only in the PR for the visibility and gettin' dem stars.

Maybe I'm way off base here, I'm old and grizzled and I think it's showing. ;p