sentry
getsentry/sentry/AGENTS.md
user requests like PR review, branch audit, and Warden follow-up. - If a downstream review harness controls the final response shape, do not hardcode a competing output format
No other project uses it yet
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.
getsentry/sentry/AGENTS.md
user requests like PR review, branch audit, and Warden follow-up. - If a downstream review harness controls the final response shape, do not hardcode a competing output format
No other project uses it yet
ColorlibHQ/AdminLTE/AGENTS.md
indentation, UTF-8, LF endings, and final newlines as defined in `.editorconfig`. Follow neighboring code and repository ESLint/Stylelint rules. Prettier is configured with single quotes, semicolons, and a 100-character
Steady2 mentions in 2 weeks
No other project uses it yet
logseq/logseq/AGENTS.md
bodies, trailers, branch names, PR titles, or PR descriptions. - PR titles must describe the code change only. - Before creating or updating commits or PRs, verify that the generated metadata does
No other project uses it yet
K-Dense-AI/scientific-agent-skills/AGENTS.md
scripts/`, or `assets/` only when they earn their place. 4. Run the commands and code you document. Scope claims to the release you actually tested ("targets stable GeoPandas
Steady4 mentions in 2 weeks
1 project uses a version of this
meteor/meteor/AGENTS.md
codebase](.github/skills/codebase/SKILL.md) | Build system, CLI, isobuild, tools/ directory | | [conventions](.github/skills/conventions/SKILL.md) | Writing packages, CLI commands, code patterns | | [testing](.github/skills/testing/SKILL.md) | Test value, planning and refinement, change scope, test layers, and focused verification
apache/spark/AGENTS.md
Apache Spark ## Pre-flight Checks Before the first code edit or running test in a session, ensure a clean working environment. DO NOT skip these checks: 1. Run `git remote
No other project uses it yet
Niko1221/Strata/AGENTS.md
server ([docs/MCP_SERVER.md](docs/MCP_SERVER.md)) offers the same steps as tools. ## Working on the code - How the engine works, every measured number, the API and all settings: [docs/DETAILS.md](docs/DETAILS.md) and the [paper
No other project uses it yet
colinhacks/zod/AGENTS.md
review the maintainer's changes — they are final, not a proposal. Don't thank them for "letting" the maintainer rewrite their work. - When posting comments with code samples
Steady5 mentions in 2 weeks
No other project uses it yet
ray-project/ray/AGENTS.md
welcome. ### Accountability - Pure code-agent PRs are **not allowed**. A human submitter must understand and defend the change end-to-end. - The submitting human must review every changed line
No other project uses it yet
ray-project/ray/doc/AGENTS.md
doc/BUILD.bazel` and the example `BUILD.bazel` files emit it, because they define test targets. Library code tags select the same steps. - **`doc_example`** is what doc assets emit: `.py`, `.ipynb`, `.yaml
No other project uses it yet
HeyPuter/puter/AGENTS.md
Understand what you commit.** AI assistance is fine; shipping code you couldn't have written, debugged, or defended in review is not. - **A limit change is not done until
No other project uses it yet
gradio-app/gradio/AGENTS.md
template. Trivial autocomplete does not need to be disclosed. All AI-generated code must be self-reviewed. 4. **Format your code before pushing.** - Backend: `bash scripts/format_backend.sh` - Frontend: `bash scripts/format_frontend.sh
Steady3 mentions in 2 weeks
No other project uses it yet
THU-MAIC/OpenMAIC/AGENTS.md
runs on every non-draft pull request. The contribution workflow is in [CONTRIBUTING.md](CONTRIBUTING.md). ## Code Review Rules ### Severity - P1 is only for problems that produce wrong behavior at runtime: user
Steady7 mentions in 2 weeks
No other project uses it yet
LizardByte/Sunshine/AGENTS.md
This limit applies only to creating issues; investigate or fix issues fully when asked. ## Code Review Rules Check new and modified tests for the common-header and include-group conventions
No other project uses it yet
sxyazi/yazi/AGENTS.md
child crate is not a new workspace dependency. Evaluate new crates by the maintained code and correctness obligations they remove versus their integration, compatibility, security, and upkeep costs; add them
No other project uses it yet
deepspeedai/DeepSpeed/AGENTS.md
enforced by the required CI check; do not report commit-signoff findings in code reviews. - Formatting: yapf (column_limit=119, `.style.yapf`) + flake8 (`.flake8`). - Always verify changed files pass pre-commit
No other project uses it yet
tinyhumansai/openhuman/AGENTS.md
# OpenHuman OpenHuman is a React and Tauri v2 desktop assistant with an in-process
No other project uses it yet
wshobson/agents/docs/agents.md
completeness, consistency, and correctness | ### Quality Assurance & Security #### Code Quality & Review | Agent | Model | Description | | ------------------------------------------------------------------------------------------------ | ----- | --------------------------------------------------------------- | | [code-reviewer](../plugins/comprehensive-review/agents/code-reviewer.md) | opus | Code review with security focus and production reliability | | [security-auditor](../plugins/comprehensive-review/agents/security-auditor.md) | opus | Vulnerability
No other project uses it yet
fastlane/fastlane/AGENTS.md
comments, and do what it asks first (an audit, a discussion) before changing code. A review checks the change against it. - One concern per pull request. - A fix comes with
No other project uses it yet
qbittorrent/qBittorrent/AGENTS.md
Wikipedia article]: https://en.wikipedia.org/wiki/BitTorrent ## Communication Use clear, appropriate English for non-native readers. ## Code Review Guidelines * Respect project configuration. \ Avoid reading excluded files unless it is strictly necessary
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.