coreutils
uutils/coreutils/AGENTS.md
AGENTS.md Writing this file is not a statement for or against using AI coding agents. People are using them in this repository either way, so this file exists to make
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
uutils/coreutils/AGENTS.md
AGENTS.md Writing this file is not a statement for or against using AI coding agents. People are using them in this repository either way, so this file exists to make
processing/p5.js/AGENTS.md
place to ask questions, and people there are really helpful! > - This project follows a Code of Conduct that you can read [here](./CODE_OF_CONDUCT.md). We want to make sure this
temporalio/temporal/AGENTS.md
experienced developer working on the temporal project. Your task is to review code, fix a bug, or implement a new feature while adhering to the project's best practices
verl-project/verl/AGENTS.md
code-assist Signed-off-by: Your Name <your.email@example.com> ``` ### Resolving agent reviews Review comments from agent bots (e.g., gemini-code-assist) can be outdated or wrong. Always verify their suggestions against
PrefectHQ/prefect/AGENTS.md
resolving issue - Brief summary: "this PR {changes}" - Details in ` ` tag - Include relevant links ## Code Review Rules When reviewing changes, read and apply [REVIEW.md](REVIEW.md). # Project Practices - All PRs require test
air-verse/air/AGENTS.md
When adding changes, do NOT break existing behavior. - Make changes small and easy to review. - Code and comments must be written in English. - Prefer root-cause fixes over band-aids
No other project uses it yet
facebook/lexical/AGENTS.md
local variable properties that lint cannot reliably detect, so they must be caught in code review. For full details on the browser platform APIs involved, see [Shadow DOM and iframes
SuperClaude-Org/SuperClaude_Framework/AGENTS.md
install` once, then `npm test` or `npm run build`; repeat for `research/` and `index/`. ## Coding Style & Naming Conventions - Python: 4-space indentation, Black line length 88, Ruff
coleam00/Archon/AGENTS.md
archon/workflow-language-constitution.md`](.archon/workflow-language-constitution.md), aspirational engineering craft and review values in [`.archon/engineering.md`](.archon/engineering.md), user documentation in the docs site, and machine-checkable rules in code, types, tests, lint, or CI. ## Read before
Steady3 mentions in 2 weeks
No other project uses it yet
JanDeDobbeleer/oh-my-posh/AGENTS.md
that file and commit it with the related change. ## Pull request reviews Validate every comment against the code. Fold each fix into the commit that introduced the code with
No other project uses it yet
wechaty/wechaty/AGENTS.md
tests and documentation. When sources disagree, trust them in this order: 1. This checkout: code, specs, [package.json](package.json), and CI workflows. 2. The installed `wechaty-puppet` package in `node_modules
saleor/saleor/AGENTS.md
post_migrate` signal used to trigger data-migration tasks — see Data Migrations below.) # Code style - Use global import statements. Place all imports at the top of the file rather than
johannesjo/super-productivity/AGENTS.md
Angular + Electron + Capacitor. ## Repo map Start with the [repository content map](docs/repository-map.md) (task keywords, code entry points, focused tests) and follow only the relevant links. Layer boundaries: [app map](src/app/README.md
marimo-team/marimo/AGENTS.md
users Being an open source library, the public API, abstractions, documentation, and the code itself are the product and deserve careful consideration. When working in this repository, you should consider
pubkey/rxdb/AGENTS.md
messages in production builds. Use the error codes from `src/rx-error.ts` and add new error codes if needed like `PL1`, `PL2`. Example: `throw newRxError('PL1', { plugin });` ## Documentation Style - SHOULD use clear
oxc-project/oxc/AGENTS.md
quality or unreviewed AI content will be closed immediately All AI-generated code must be thoroughly reviewed, tested, and understood by the contributor before submission. Code should meet
dotnet/maui/AGENTS.md
work, including .NET 12 fixes | `main` | | .NET 11 servicing fixes | Literal `net11`, for review | | Older servicing, release integration, infrastructure, or documentation | The branch designated for that work; do not guess
comet-ml/opik/AGENTS.md
ignore this directory and use `.agents/` as the canonical source. - `.github/copilot-instructions.md` is GitHub Copilot code review guidance only. ## Security & Configuration Tips - Keep secrets and API keys out of source control
Steady6 mentions in 2 weeks
No other project uses it yet
czlonkowski/n8n-mcp/AGENTS.md
every code change and `npm run build` after MCP server changes. - After rebuilding server code, ask the user to reload the MCP server before testing the changed MCP behavior. - Name
Steady9 mentions in 2 weeks
No other project uses it yet
steipete/CodexBar/AGENTS.md
cold-build comparison, or maintainer-requested cleanup. - Run focused tests during development; the final code needs focused tests plus `make check`, with the full suite from
Steady3 mentions in 2 weeks
No other project uses it yet
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.