Skip to content

docs(#3510): add AGENTS.md guidance for review conventions - #3511

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/3510-agents-md-review-guidance
Open

docs(#3510): add AGENTS.md guidance for review conventions#3511
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/3510-agents-md-review-guidance

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

What:

Add two new sections to AGENTS.md to prevent false-positive review findings:

  1. Go file header convention — Documents the repo-wide pattern of placing SPDX license headers before //go:build tags. Review agents (fullsend and qodo) were flagging this as a style violation on PR Use ValidateVSAAndComparePolicy for ec validate image VSA skip #3489, but it is an intentional convention across all Go files.

  2. Security fix review expectations — Instructs review agents to flag documentation gaps (e.g., missing THREAT_MODEL.md or DESIGN.md updates) as informational comments rather than blocking change requests when the PR's primary purpose is a security fix. On PR Use ValidateVSAAndComparePolicy for ec validate image VSA skip #3489, the review agent issued REQUEST_CHANGES verdicts in 6 of 10 review cycles for doc gaps on a security fix that both human reviewers considered non-blocking.

Why:

Both findings from PR #3489 were technically correct but miscalibrated for this repo's conventions. The build-tag false positive is a straightforward convention gap. The documentation severity miscalibration creates friction and teaches authors to ignore agent verdicts. Adding AGENTS.md guidance follows the established pattern in this repo (#3503, #3508, #3451, #3389, #3458).

Tickets:


Closes #3510

Post-script verification

  • Branch is not main/master (agent/3510-agents-md-review-guidance)
  • Secret scan passed (gitleaks — a18338416237ca7c5154a0af499f81d4b821ea46..HEAD)
  • PR body secret scan passed (gitleaks — no-git)

Add two sections to AGENTS.md to prevent false-positive review
findings:

1. Go file header convention: documents the repo-wide pattern
of placing SPDX license headers before //go:build tags, so
review agents do not flag this as a style violation.

2. Security fix review expectations: instructs review agents
to flag documentation gaps as informational comments rather
than blocking change requests on security-fix PRs.

Both patterns were identified from PR #3489 where review agents
issued miscalibrated findings. This follows the established
pattern of adding AGENTS.md guidance to improve agent review
accuracy (similar to #3503, #3508, #3451, #3389, #3458).

Note: pre-commit could not run in sandbox (network restriction).
The post-script runs it authoritatively.

Closes #3510
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 19, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 3:03 PM UTC · Completed 3:13 PM UTC

Commit: 87c4a29 · View workflow run →

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

Medium


Labels: PR modifies agent guidance documentation (AGENTS.md)

@fullsend-ai-review fullsend-ai-review Bot added requires-manual-review Review requires human judgment documentation Improvements or additions to documentation agentic labels Aug 19, 2026
@codecov

codecov Bot commented Aug 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
acceptance 54.46% <ø> (ø)
generative 12.27% <ø> (ø)
integration 23.59% <ø> (ø)
unit 72.21% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agentic documentation Improvements or additions to documentation requires-manual-review Review requires human judgment size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add AGENTS.md guidance for Go file header conventions and security-fix review expectations

0 participants