homebrew-cask
Homebrew/homebrew-cask/AGENTS.md
Agent Instructions for homebrew-cask This document helps coding agents produce high-quality PRs for Homebrew Cask contributions. ## Before Any PR 1. **Check for existing PRs** for the same cask
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.
Homebrew/homebrew-cask/AGENTS.md
Agent Instructions for homebrew-cask This document helps coding agents produce high-quality PRs for Homebrew Cask contributions. ## Before Any PR 1. **Check for existing PRs** for the same cask
dyad-sh/dyad/AGENTS.md
will run against stale code and results will be misleading. Only changes to test code itself (e.g. files in `e2e-tests/`) do not require a rebuild. See [rules/e2e-testing.md](rules/e2e-testing.md
Steady5 mentions in 2 weeks
No other project uses it yet
handsontable/handsontable/AGENTS.md
evals/README.md` | | Step-by-step task workflows | `.claude/skills/` (e.g., `handsontable-dev`, `handsontable-plugin-dev`, `handsontable-code-review`, `pr-creation`) | `.ai/` reference locations: | `.ai/` location | Scope | |---|---| | `.ai/` (root) | Monorepo — stack, structure, build
handsontable/handsontable/visual-tests/AGENTS.md
creating-visual-test-examples` skills, the PR template, the `pr-creation` and `handsontable-code-review` skills, `.ai/LOCAL-ENFORCEMENT.md`) carries one sentence and a link here. `.github/scripts/__tests__/visual-decision-rule.test.mjs` pins the paragraph to this
QwikDev/qwik/AGENTS.md
grown out of that shape, rewrite it into that order before review instead of stacking fix-up commits. ### Code Quality #### Sanity - Remember to keep your code DRY. - Do not leave
QwikDev/qwik/.ruler/AGENTS.md
grown out of that shape, rewrite it into that order before review instead of stacking fix-up commits. ### Code Quality #### Sanity - Remember to keep your code DRY. - Do not leave
matomo-org/matomo/AGENTS.md
specific skills when those skills are available. It is intended for: - AI coding agents - Matomo core engineers - Reviewers looking for a shared baseline This is not a generic PHP guide
gitbutlerapp/gitbutler/AGENTS.md
reviewable changes; avoid unrelated rewrites. - Use the simplest design that solves the actual problem; do not add speculative machinery, and remove machinery your change makes unnecessary. - Inspect nearby code before
gitbutlerapp/gitbutler/crates/AGENTS.md
snapshot-based; do not design bespoke inverse operations for it. - Before changing or reviewing code that derives graph/workspace/branch/stack/commit relationships, reachability, dependencies, ordering, operation targets, or Git graph/history/ref-placement mutations, use `crates/WORKSPACE_MODEL.md
No other project uses it yet
huggingface/peft/.ai/AGENTS.md
read `tests/README.md` for detailed instructions on testing in PEFT. Test code that is improperly implemented imposes a big review burden on maintainers. #### Test selection If you make a testable change
netbox-community/netbox/AGENTS.md
short: - AI tools may be used to explore the codebase and to generate code. - The contributor must fully understand, and be able to explain, every change submitted. - Issues, pull request
1jehuang/jcode/AGENTS.md
finish and integrate safely rather than switching blindly. When the user asks you to review or integrate a PR or branch, you may inspect, test, and integrate that contribution regardless
Steady5 mentions in 2 weeks
No other project uses it yet
eclipse-theia/theia/AGENTS.md
Code APIs that were previously "proposed" are now stable (e.g., workspace trust). Check VS Code's current API status before creating proposed API files. ## Styling Theia permits extensive color theming
oracle/graal/docs/AGENTS.md
Graal repo. Ask your agent to consult it before drafting, rewriting, or reviewing documentation so it can follow GraalVM documentation conventions for terminology, tone, spelling, and Markdown structure. Apply these
oracle/graal/substratevm/AGENTS.md
suffices; regex support increases image code size. - When porting HotSpot code, preserve its names and structure where practical so reviewers and maintainers can compare the implementations. - If you touch documented
NVIDIA/OpenShell/AGENTS.md
first. We design systems and use agents to implement them — this is not vibe coding. The product provides safe, sandboxed runtimes for autonomous AI agents, and the project itself
Steady10 mentions in 2 weeks
No other project uses it yet
xbmc/xbmc/AGENTS.md
free simply because it is easy to produce. Optimize for code that needs to exist and can be reviewed and maintained. ## Release stabilization When working on a release branch
containerd/containerd/AGENTS.md
guide's [Coding Agent Usage](https://github.com/containerd/project/blob/main/CONTRIBUTING.md#coding-agent-usage) policy and the repository's [submission requirements](CONTRIBUTING.md#automated-and-ai-generated-contributions). The human contributor reviews all content before submission
github/docs/content/copilot/responsible-use/agents.md
GitHub Copilot includes several agentic features that go beyond suggestion and conversation—they can review code, take action on your behalf, and build applications. This card covers the following experiences
pydantic/pydantic-ai/AGENTS.md
slow and CI covers them at the right time. # Coding Guidelines When generating or reviewing code anywhere in this repo, always read [agent_docs/index.md](agent_docs/index.md) and follow/enforce those guidelines
Steady2 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.