agents: Do not remove comments that already exist

[patrickelectric]

Summary by Sourcery

Documentation:

• Document that existing comments should be preserved when refactoring code that is not logically changed.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates AGENTS guidelines to require preserving existing comments when refactoring untouched logic.

File-Level Changes

Change	Details	Files
Document new guideline about preserving existing comments during refactors.	Add rule clarifying that existing comments should not be deleted when refactoring code whose logic is unchanged Keep surrounding coding-style and documentation rules intact to maintain context	AGENTS.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• The new guideline about preserving existing comments could be clearer about exceptions (e.g., when comments are incorrect, redundant, or violate the “no what-comments” rule) to avoid confusion when refactoring legacy code.
• Consider tightening the wording of the new line (e.g., splitting into two sentences or removing the comma after 'comments') to improve readability and keep it consistent with the style of the surrounding bullets.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new guideline about preserving existing comments could be clearer about exceptions (e.g., when comments are incorrect, redundant, or violate the “no what-comments” rule) to avoid confusion when refactoring legacy code.
- Consider tightening the wording of the new line (e.g., splitting into two sentences or removing the comma after 'comments') to improve readability and keep it consistent with the style of the surrounding bullets.

## Individual Comments

### Comment 1
<location> `AGENTS.md:48` </location>
<code_context>
 - Use 120 character line length
 - No docstrings unless the function is non-obvious
 - No comments unless explaining "why", never "what"
+- Preserve existing comments, when refactoring code, do not delete comments from code you haven't logically changed
 - Prefer editing existing files over creating new ones
 - Use optional chaining (`?.`) when possible in typescript
</code_context>

<issue_to_address>
**issue (typo):** Consider fixing the comma splice by adjusting punctuation or restructuring the sentence.

This sentence currently has a comma splice. For example, you could rewrite it as: "Preserve existing comments when refactoring code; do not delete comments from code you haven't logically changed" or "When refactoring code, preserve existing comments and do not delete comments from code you haven't logically changed."

```suggestion
- Preserve existing comments when refactoring code; do not delete comments from code you haven't logically changed
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}