Skip to content

docs: add AGENTS.md with agent contribution guardrails - #968

Draft
dims wants to merge 1 commit into
mainfrom
add-agents-md
Draft

docs: add AGENTS.md with agent contribution guardrails#968
dims wants to merge 1 commit into
mainfrom
add-agents-md

Conversation

@dims

@dims dims commented Aug 13, 2026

Copy link
Copy Markdown

Summary

  • Add AGENTS.md as the agent-facing entry point for AI coding agents working in this repo.
  • Rules are distilled from NVIDIA repos that have established AGENTS.md files (Megatron-LM, garak, cuda-python, dcgm-exporter, Model-Optimizer, cudnn-frontend, and others) and calibrated against patterns observed from bulk AI-generated PRs on this repo.

Key guardrails

  • Duplicate check before opening any PR (gh pr list + gh issue list).
  • Issue-first when five or more instances of the same pattern exist.
  • Max three PRs per session to protect shared CI capacity.
  • One PR per root cause, not one per distro directory — cross-distro fixes go in a single PR.
  • Correctness and cosmetic changes in separate PRs.
  • Every PR must link to an issue and be opened as a draft.
  • Tests must execute code, not grep for old patterns.
  • No git push or gh pr create without explicit human approval.
  • Fail-closed: stop and report when any guardrail triggers.

Related

Related to #967 (CONTRIBUTING.md PR guidelines).

Distill practices from NVIDIA repos that have AGENTS.md (Megatron-LM,
garak, cuda-python, dcgm-exporter, Model-Optimizer, and others) and
combine with patterns observed from bulk AI-generated PR floods on this
repo.

Key rules:
- duplicate check required before opening any PR
- issue-first for five or more instances of the same pattern
- max three PRs per agent session to protect shared CI
- one PR per root cause, not one PR per distro directory
- correctness and cosmetic fixes in separate PRs
- every PR must link to an issue and be opened as a draft
- tests must execute code, not grep for old patterns
- no push or pr create without explicit human approval
- fail-closed: stop and report when any guardrail triggers

Signed-off-by: Davanum Srinivas <[email protected]>
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