AGENTS.md examples from real projects

mem0aiReads credentialsAGENTS.md

mem0

mem0ai/mem0/AGENTS.md

template asks how the *code* was written; drafting the description with a model is fine. The disclosure is never held against you, it tells a reviewer where to look. Silence

No other project uses it yet

mem0aiReads credentialsAGENTS.md

mem0

mem0ai/mem0/.github/AGENTS.md

enforces squash-only merges, linear history, no deletion, no force-push, and one approving review. Two status checks belong in its `required_status_checks` rule: | Context | Posted

No other project uses it yet

scikit-learnAGENTS.md

scikit-learn

scikit-learn/scikit-learn/AGENTS.md

This pull request includes code written with the assistance of AI. > The code has **not yet been reviewed** by a human. This is a **mandatory requirement**, not optional. Include

No other project uses it yet

ZhuLinsenReads credentialsAGENTS.md

daily_stock_analysis

ZhuLinsen/daily_stock_analysis/AGENTS.md

不一致等问题，维护者可以要求关闭重做，而不是继续逐点 review。 ## 2. AI 协作资产治理 - `AGENTS.md` 是仓库内 AI 协作规则的唯一真源。 - `CLAUDE.md` 必须是指向 `AGENTS.md` 的软链接，用于兼容 Claude 生态。 - `.github/copilot-instructions.md` 与 `.github/instructions/*.instructions.md` 是 GitHub Copilot / Coding Agent 的镜像或分层补充；若与本文件冲突

No other project uses it yet

prometheusAGENTS.md

prometheus

prometheus/prometheus/AGENTS.md

supporting analysis (Google Doc, issue, etc.) for complex changes. --- ## Code Style - Follow [Go Code Review Comments](https://go.dev/wiki/CodeReviewComments) and the formatting/style section of [Go: Best Practices for Production Environments

No other project uses it yet

mvanhornReads credentialsAGENTS.md

last30days-skill

mvanhorn/last30days-skill/AGENTS.md

GitHub device auth is a two-command split: `setup --github-start` returns the code fast (foreground, copies to clipboard), `setup --github-poll` waits for authorization (`setup --github` chains both

No other project uses it yet

facebookAGENTS.md

docusaurus

facebook/docusaurus/AGENTS.md

check its presence to know which rules to apply. ### General rules - Humans review all the code: always write code that is easy to read and review, following the [`code-style

No other project uses it yet

webpackDeletes or force-pushesAGENTS.md

webpack

webpack/webpack/AGENTS.md

real before/after (code, output, size, memory or CPU) under **Summary**. - **Subscribe to every PR you open**; unsubscribe once CI is green and every automated review is handled, or the requester

No other project uses it yet

warpdotdevAGENTS.md

Warp

warpdotdev/Warp/AGENTS.md

feedback; defer checks and tests until after implementation where possible. 2. Once the code and self-review are complete, run the relevant tests and fix the code until they pass

coollabsioReads credentialsAGENTS.md

coolify

coollabsio/coolify/AGENTS.md

artisan test --compact --filter=testName # single test php artisan test --compact tests/Feature/SomeTest.php # specific file # Code formatting (Pint, Laravel preset) vendor/bin/pint --dirty --format agent # format changed files # Frontend

No other project uses it yet

traefikAGENTS.md

traefik

traefik/traefik/AGENTS.md

answer *why*, not *what*.** Comments that restate what the code already says are noise: they go stale and waste review time. Only add a comment when it records

No other project uses it yet

scrapyAGENTS.md

scrapy

scrapy/scrapy/AGENTS.md

only on what it has as well. - Review your own diff. Remove whatever the change does not need: unused parameters, dead code, leftover debugging, comments that restate the code. ## Code

No other project uses it yet

gsd-buildAGENTS.md

get-shit-done

gsd-build/get-shit-done/docs/AGENTS.md

agents** detailed in this section. Twelve additional shipped agents (pattern-mapper, debug-session-manager, code-reviewer, code-fixer, ai-researcher, domain-researcher, eval-planner, eval-auditor, framework-selector, intel-updater

usememosAGENTS.md

memos

usememos/memos/AGENTS.md

response redaction. Black-box service tests live in `server/api/test/`, unit tests next to the code. ## Change Routing | Change | Update | Verify | | --- | --- | --- | | Go service or router behavior | Handlers under `server/`, rules under

No other project uses it yet

gitAGENTS.md

git / po

git/git/po/AGENTS.md

Reviewing translation quality ## Background knowledge for localization workflows Essential background for the workflows below; understand these concepts before performing any housekeeping tasks in this document. ### Language code and notation

withastroAGENTS.md

astro

withastro/astro/AGENTS.md

narrate change history ("now", "previously", "no longer") and never address the reviewer ("this correctly handles..."). State how the code works, not how it came to be or why the change

No other project uses it yet

ultralyticsAGENTS.md

ultralytics

ultralytics/ultralytics/AGENTS.md

intentionally removes them with evidence. **Review gate:** for every addition, the reviewer decides whether deleting or changing existing code would have fixed the problem instead — if it would, that

No other project uses it yet

BerriAIPipes a download into a shellAGENTS.md

litellm

BerriAI/litellm/AGENTS.md

requesting maintainer review, verify the current PR tip passes required CI and code coverage and has acceptable reviews from the review bots on the PR, such as Veria and Bugbot

No other project uses it yet

tw93AGENTS.md

Pake

tw93/Pake/AGENTS.md

same source of truth. Local-only overrides (`CLAUDE.local.md`, `AGENTS.override.md`, `.claude/settings.local.json`) stay ignored. ## Code Conventions - No Chinese comments in any source (Rust / TypeScript / any file). Comments and identifiers in English; follow

No other project uses it yet

penpotAGENTS.md

penpot

penpot/penpot/AGENTS.md

Writing rules, from Orwell, 1946. These govern prose: docs, PR text, messages. Never touch code or technical terms; swap in everyday words only where precision survives. 1. Never

No other project uses it yet