AGENTS.md examples from real projects

pandas-devAGENTS.md

pandas

pandas-dev/pandas/AGENTS.md

limited to, interactions such as pushing code, opening issues or pull requests, and replying to issues, pull requests, or reviews. - The user is required to disclose your agent information (harness

mudlerAGENTS.md

LocalAI

mudler/LocalAI/AGENTS.md

MODEL_VERSION [TOOL1] [TOOL2]`. - **The human submitter is responsible** for reviewing, testing, and understanding every line of generated code. ## Topics | File | When to read | |------|-------------| | [.agents/ai-coding-assistants.md](.agents/ai-coding-assistants.md) | Policy for AI-assisted

metabaseAGENTS.md

metabase

metabase/metabase/AGENTS.md

changelog for breaking API changes. # Skills For detailed guidance on writing and reviewing code and documentation, see the skills in [.claude/skills/](.claude/skills/): ## Clojure ### clojure-mcp tools - **[clojure-eval](.claude/skills/clojure-eval/SKILL.md)** - Always

No other project uses it yet

metabaseAGENTS.md

metabase / frontend

metabase/metabase/frontend/AGENTS.md

Package manager**: Bun - **Build**: Rspack (primary), Webpack (legacy) - **Testing**: Jest + React Testing Library, Cypress ## Coding Standards @../docs/developers-guide/frontend.md Read `docs/developers-guide/frontend.md` before frontend work — it's the detailed guide imported above. ### Load

No other project uses it yet

HomebrewAGENTS.md

brew

Homebrew/brew/docs/AGENTS.md

last_review_date: "2026-06-10" --- # Agent Instructions for Homebrew/brew docs These instructions apply when working in `docs/`. ## Tooling - Use the system Homebrew `brew bundle exec ...` workflow from this directory

No other project uses it yet

calcomReads credentialsAGENTS.md

cal.com

calcom/cal.com/AGENTS.md

self-contained PRs that are easier to understand and review. ### Size Limits - **Lines changed**: Keep PRs under 500 lines of code (additions + deletions) - **Files changed**: Keep PRs under 10 code

JuliaLangAGENTS.md

julia

JuliaLang/julia/AGENTS.md

when relevant; otherwise read the canonical `SKILL.md` directly. - [`doc/src/devdocs/agents/skills/doctests/`](doc/src/devdocs/agents/skills/doctests/SKILL.md) — writing and verifying `jldoctest` code blocks. - [`doc/src/devdocs/agents/skills/test-changes/`](doc/src/devdocs/agents/skills/test-changes/SKILL.md) — running and updating tests after changing them. - [`doc/src/devdocs/agents/skills/c-static-analysis/`](doc/src/devdocs/agents/skills/c-static-analysis/SKILL.md) — Clang static analysis

No other project uses it yet

abhigyanpatwariReads credentialsAGENTS.md

GitNexus

abhigyanpatwari/GitNexus/AGENTS.md

package (`gitnexus/skills/`, installed to editor targets by `gitnexus setup`) and the Claude Code plugin; review also has a standalone Cursor mirror. `gitnexus/test/unit/shipped-skills-sync.test.ts` guards the copies. Token savings of the workflow

No other project uses it yet

paperless-ngxAGENTS.md

paperless-ngx

paperless-ngx/paperless-ngx/AGENTS.md

before investing in implementation and review. - Issue reports must describe observed behavior, reproduction steps, and relevant logs. Do not add speculative root causes, code analysis, or proposed fixes to agent

gogsAGENTS.md

gogs

gogs/gogs/AGENTS.md

incompetent you are. Do it right on your first try, fact-check and review after changes. If you are not sure, ask for help. - When you see changes made outside

No other project uses it yet

momentAGENTS.md

moment

moment/moment/AGENTS.md

standalone runtime smoke test must remain executable on Node 8, and generated library code must continue to pass the runtime compatibility workflow. Moment has no runtime dependencies

No other project uses it yet

apacheAGENTS.md

airflow

apache/airflow/AGENTS.md

selected project in the monorepo with only dependencies that it has ## Security Model When reviewing code, writing security documentation, or performing security research, keep in mind the following aspects

apacheAGENTS.md

airflow / providers

apache/airflow/providers/AGENTS.md

When reviewing provider PRs Flag any of these patterns: - `**conn.extra_dejson` or `**self.extra_dejson` spread into a constructor or call. - Looping over `conn.extra_dejson.items()` and forwarding every key. - New code paths

No other project uses it yet

siyuan-noteAGENTS.md

siyuan

siyuan-note/siyuan/AGENTS.md

maintenance - **Final frontend checks:** After frontend code changes, run `pnpm run lint` in `app/` (types, auto-fixing ESLint, CSS/menu/startup-language checks, not behavioral tests). Review its diff, keeping fixes in scope

ogulcancelikAGENTS.md

herdr

ogulcancelik/herdr/AGENTS.md

already split into state, actions, and input. Keep it that way. - **Platform code is isolated.** OS-specific behavior lives in the matching `src/platform/ .rs` file, with only shared traits, types

danny-avilaAGENTS.md

LibreChat

danny-avila/LibreChat/AGENTS.md

Keep only what the change carries, and describe the code as it stands rather than narrating earlier commits or review rounds. Naming the merged pull request that caused

omacomReads credentialsAGENTS.md

omarchy

omacom/omarchy/AGENTS.md

being implemented, or where direct package-manager behavior is required. # Background Work - Long-running code (the shell, daemons, watchers) reacts to events instead of polling with a timer. Polling

cliAGENTS.md

cli

cli/cli/AGENTS.md

commit, push, or publish merely because implementation is complete. For PR review, use [code-review](.github/skills/code-review/SKILL.md). For sandboxed reproductions with `ghmock`, use [ghmock](.github/skills/ghmock/SKILL.md). For authorized maintainer debt maintenance

No other project uses it yet

DIYgodAGENTS.md

RSSHub

DIYgod/RSSHub/AGENTS.md

Review Comments**: Before requesting re-review, ensure all previous review comments are addressed, not just some of them. ### Code Organization 45. **Move Functions Up**: Move function definitions to the highest

No other project uses it yet

AstrBotDevsAGENTS.md

AstrBot

AstrBotDevs/AstrBot/AGENTS.md

After finishing, use `ruff format .` and `ruff check .` to format and check the code. 4. When committing, ensure to use conventional commits messages, such as `feat: add new agent

No other project uses it yet