Skip to content

chore: Document that agents must not reformat unrelated C# code - #2008

Closed
hatayama wants to merge 1 commit into
chore/public-candidate-triagefrom
docs/agent-formatting-rule
Closed

hatayama wants to merge 1 commit into
chore/public-candidate-triagefrom
docs/agent-formatting-rule

Conversation

@hatayama

@hatayama hatayama commented Jul 25, 2026 •

Copy link
Copy Markdown
Owner

Summary

Context

During PR-5 triage, an agent rewrite collapsed multi-line call sites into one-liners and made the real deletion unreviewable. The durable fix is an explicit agent instruction (CLAUDE.md is a symlink to AGENTS.md).

Test plan

  • Confirm the PR touches only AGENTS.md (+4 lines)
  • Confirm wording matches the intended no-reformat / no-collapse-rewrite policy

Review in cubic

Surgical triage edits were collapsed into unreviewable one-liners by
agent rewrite scripts. Record the no-reformat rule in AGENTS.md so
future diffs stay scoped to the requested change.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@hatayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3b3eb389-37da-4a87-b1d7-c88efb53a282

📥 Commits

Reviewing files that changed from the base of the PR and between e4adacb and 12fd521.

📒 Files selected for processing (1)
  • AGENTS.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/agent-formatting-rule

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@hatayama

Copy link
Copy Markdown
Owner Author

Closing per repository owner decision: do not add the AGENTS.md formatting rule.

Equivalent guidance already exists in global agent settings; adding a duplicate rule to AGENTS.md would dilute attention. The no-unrelated-reformat policy remains in force for triage work without an AGENTS.md change.

@hatayama hatayama closed this Jul 25, 2026
@hatayama
hatayama deleted the docs/agent-formatting-rule branch July 25, 2026 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant