AGENTS.md examples from real projects

yetoneAGENTS.md

magpie

yetone/magpie/AGENTS.md

follow the same page's documentation update, semantic change description, and review rules. ## Code standards Write and review changes against the [code standards](docs/code-standards.md). ## Community PRs Before reviewing a community

BlockReads credentialsAGENTS.md

sprout

block/sprout/AGENTS.md

they are defects authors agree with on sight. Authors apply them **before writing code**, and reviewers check against them; each cites the PRs where reviewers litigated it. Rules mined from

utmappAGENTS.md

UTM

utmapp/UTM/AGENTS.md

protocol — `UTMQemuVirtualMachine` (QEMU, via the QEMUKit/CocoaSpice packages) and `UTMAppleVirtualMachine` (Virtualization.framework, macOS-only). Most backend code branches on which. - **Config is the serialization format** — parallel `Codable` trees `UTMQemuConfiguration` and `UTMAppleConfiguration` (PLIST

jdxReads credentialsAGENTS.md

mise

jdx/mise/AGENTS.md

core`, `deps`, `ci` - Use `task` (not `run`) for task-related changes, even if the code lives in `src/cli/run.rs` or `src/cmd.rs` **Description Style:** - Start the description with a lowercase character

rustfsAGENTS.md

rustfs

rustfs/rustfs/AGENTS.md

artifact-heavy work, read [implementation and Rust style rules](.agents/references/implementation.md). For a read-only code review, use its change-style and boundary sections as needed. - Before commits, pushes, PR creation/updates

No other project uses it yet

rustfsAGENTS.md

rustfs / crates

rustfs/rustfs/crates/AGENTS.md

uses multiple locks. Never acquire the same set of locks in different orders across code paths. - Never hold a `tokio::sync::RwLock`/`Mutex` write guard across `.await` points unless

No other project uses it yet

FreeCADAGENTS.md

FreeCAD

FreeCAD/FreeCAD/AGENTS.md

tests, validate a fix, or diagnose CI | [Testing and validation](contrib/guidelines/testing-and-validation.md) | | Review completed code | [Reviewing changes](contrib/guidelines/reviewing-changes.md) | | Prepare commits or address review feedback | [Contributing changes](contrib/guidelines/contributing-changes.md) | Review code after writing

anywhere-labsAGENTS.md

deepseek-harness-desktop

anywhere-labs/deepseek-harness-desktop/AGENTS.md

variant's upstream-family files export the same names as `undefined`, and the shared code skips the feature. Once both follow the same release they must mirror again. - Run upstream

nettyAGENTS.md

netty

netty/netty/AGENTS.md

work back, say what you changed and what you verified, so the human can review it properly. ## Branches and Java baselines | Branch | Role | Java baseline | | ------ | ---- | ------------- | | 4.1 | maintenance, bug fixes only

qarminAGENTS.md

czkawka

qarmin/czkawka/AGENTS.md

just fix` produces any output on stderr or exits non-zero the code is not ready for review. --- ## Workspace Structure ``` czkawka/ ├── czkawka_core/ # Scanning logic – shared library used

Hugging FaceAGENTS.md

diffusers

huggingface/diffusers/.ai/AGENTS.md

post to GitHub directly** — no comments, reviews, or replies. Draft when asked and hand the text to the user. ## Code formatting - `make style` and `make fix-copies` should

No other project uses it yet

SeleniumHQAGENTS.md

selenium

SeleniumHQ/selenium/AGENTS.md

Grid routing/distributor/queue logic ## After making code changes - Call out any high risk areas touched - Note cross-binding impact and any follow-up issues needed ## Reviewing pull requests See `.github/pr_review.md

No other project uses it yet

GitlawbAGENTS.md

openclaude

Gitlawb/openclaude/AGENTS.md

working in the OpenClaude repository. Read it before changing code, and also follow [CONTRIBUTING.md](CONTRIBUTING.md) for contributor policy, PR expectations, review follow-up, and project scope. ## Project Snapshot OpenClaude

k3s-ioAGENTS.md

k3s

k3s-io/k3s/.agents/AGENTS.md

Use when: browsing or selecting local k3s agentic workflows from this folder. Catalog of workflow folders and contract for cross-tool compatibility.

No other project uses it yet

swc-projectAGENTS.md

swc

swc-project/swc/AGENTS.md

continue. ## Code style - Write comments and documentations in English. - Write documentation for your code. - When introducing a workaround, leave sufficient comments explaining why it is needed and any known limitations

apacheAGENTS.md

kafka

apache/kafka/AGENTS.md

checkstyleMain checkstyleTest spotlessCheck ./gradlew spotbugsMain spotbugsTest -x test # optional static analysis ``` Checkstyle reports: ` /build/reports/checkstyle/`. ## Coding conventions - **Commits / PR titles**: Start with `KAFKA-XXXXX`, `MINOR`, or `HOTFIX`. Use `KAFKA-XXXXX` only

iOfficeAIAGENTS.md

AionUi

iOfficeAI/AionUi/AGENTS.md

path aliases: `@/*`, `@process/*`, `@renderer/*` - Prefer `type` over `interface` (per Oxlint config) - English for code comments; JSDoc for public functions ### Internationalization (i18n) New or changed user-facing text must use i18n

No other project uses it yet

hiddifyAGENTS.md

hiddify-app

hiddify/hiddify-app/AGENTS.md

data or migration risk. Otherwise **Needs review**, saying what to look at. - **Complexity Simple**: small, one area, no native code, migration, or API change. **Complex**: several areas, native code, connection/core

No other project uses it yet

OWASPAGENTS.md

CheatSheetSeries

OWASP/CheatSheetSeries/AGENTS.md

security review and testing. Illustrative status does not excuse incorrect or insecure guidance. - When reviewing code-heavy contributions, request a shorter conceptual revision with upstream implementation links. Successful execution

Yeachan-HeoAGENTS.md

oh-my-codex / templates

Yeachan-Heo/oh-my-codex/templates/AGENTS.md

still marks that skill active. Use explicit team orchestration for feature development, bug investigation, code review, UX audit, and similar multi-lane work when coordination value outweighs overhead. Team mode