Skip to content

Document review-comment style and approval gate in AGENTS.md#1397

Merged
cristianrgreco merged 1 commit into
mainfrom
claude/dazzling-sanderson-97ef80
Jul 1, 2026
Merged

Document review-comment style and approval gate in AGENTS.md#1397
cristianrgreco merged 1 commit into
mainfrom
claude/dazzling-sanderson-97ef80

Conversation

@cristianrgreco

Copy link
Copy Markdown
Collaborator

Summary

Adds guidance to the PR Review section of AGENTS.md so PR review feedback from contributors and coding agents is consistent and low-noise. Prompted by a review where comments were overly verbose and one made a repo-wide convention claim that wasn't accurate.

New guidance:

  • Approval gate — get explicit user approval before posting any review feedback to GitHub, even when explicitly asked to review a PR. Clarifies that "review this PR" is not itself standing approval to post, and ties back to existing PR Process step 6.
  • Terse, actionable comments — state the problem, at most a sentence of context, and what to do instead; skip restated background, meta-commentary, and severity labels.
  • Inline over body — anchor comments on the relevant line; keep the summary body to must-address points plus any high-level design note.
  • Verify conventions first — only claim a convention violation after checking the rest of the repo; prefer scoping to a concrete inconsistency over a broad assertion.

Why

Review comments were verbose and not consistently actionable for the PR author, and a "no one does X" claim turned out to be wrong on closer inspection. Encoding these expectations in AGENTS.md keeps future reviews focused and prevents low-value or inaccurate comments.

Changes

  • AGENTS.md — docs-only addition to the ## PR Review section.

Verification

Docs-only change (no code, no public API). No build/test impact.

Semver

Not breaking — documentation-only change to contributor guidance.

Add guidance to the PR Review section so review feedback is consistent
and low-noise:

- Get explicit user approval before posting any review feedback to
  GitHub, even when asked to review a PR (clarifies PR Process step 6).
- Keep each comment terse: problem, minimal context, what to do instead.
- Anchor comments inline; keep the summary body to must-address points.
- Verify against the rest of the repo before claiming a convention
  violation; scope to concrete inconsistencies.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@netlify

netlify Bot commented Jul 1, 2026

Copy link
Copy Markdown

Deploy Preview for testcontainers-node ready!

Name Link
🔨 Latest commit c63bc6a
🔍 Latest deploy log https://app.netlify.com/projects/testcontainers-node/deploys/6a44cd7cd3fe550008528cd9
😎 Deploy Preview https://deploy-preview-1397--testcontainers-node.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@cristianrgreco cristianrgreco added documentation Changes to documentation patch Backward compatible bug fix labels Jul 1, 2026
@cristianrgreco cristianrgreco merged commit 91fb18c into main Jul 1, 2026
13 checks passed
@cristianrgreco cristianrgreco deleted the claude/dazzling-sanderson-97ef80 branch July 1, 2026 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Changes to documentation patch Backward compatible bug fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant