AGENTS.md examples from real projects

Wox-launcherAGENTS.md

Wox

Wox-launcher/Wox/AGENTS.md

with 100% certainty, you can start by adding log statements to the relevant code and reviewing the logs to identify the problem. The log output should contain sufficient information

eslintAGENTS.md

eslint

eslint/eslint/AGENTS.md

tests and reviews enforce them. - `bin/eslint.js` → `lib/cli.js` → `lib/eslint/eslint.js` → `lib/linter/linter.js` → `lib/rules/*.js` - **`lib/cli.js`** is the only place that reads argv, writes to the console, and sets exit codes

hashcatDeletes or force-pushesAGENTS.md

hashcat

hashcat/hashcat/AGENTS.md

code you edited. ## Never present output you did not run Every command, hash, exit code and line of output in a commit message, a pull request or an issue

No other project uses it yet

promptfooReads credentialsAGENTS.md

promptfoo

promptfoo/promptfoo/AGENTS.md

local secrets and the file exists. Review the output file for `success`, `score`, and `error` fields. With the default pass-rate threshold, exit code 0 means the eval

No other project uses it yet

icsharpcodeAGENTS.md

ILSpy

icsharpcode/ILSpy/AGENTS.md

Debug Steps pane), so run it from a local build, not the installed tool. ## Code review - **A PR review and exploratory testing are different jobs.** A review is scoped

No other project uses it yet

angularReads credentialsAGENTS.md

angular-cli

angular/angular-cli/AGENTS.md

titles. ## Building - Make a local build of all packages: ```shell pnpm build --local ``` ## Coding Practices - **Imports:** - Always use the `node:` protocol for Node.js built-in imports (e.g., `node:fs`, `node

deepset-aiReads credentialsAGENTS.md

haystack

deepset-ai/haystack/AGENTS.md

tell them instead of opening another. In addition, there are rules inferred from previous code reviews. Follow them like a reviewer's note: they encode reasons, not ceremony, so when

MicrosoftAGENTS.md

winget-cli

microsoft/winget-cli/AGENTS.md

open a pull request or link a branch when code is available. ## Pull requests Before opening a pull request: 1. Review `CONTRIBUTING.md` and follow the repository PR template. 2. Keep

apacheAGENTS.md

flink

apache/flink/AGENTS.md

tests that do not exercise the change, padded commit messages) will be closed without review ## Code Review Guidelines When reviewing a PR or diff against this repo: - Look for opportunities

earthtojakePipes a download into a shellAGENTS.md

text-to-cad

earthtojake/text-to-cad/AGENTS.md

that covers the change. Use broad wrappers when touching shared surfaces or before handoff: - Code tests: `scripts/test/test.sh` (JS, API, Python, then policy). - Focused runners: `scripts/test/test-js.sh`, `scripts/test/test-api.sh`, `scripts/test/test-docs.sh`, `scripts/test/test-python.sh`, `scripts/test/test-global.sh`. `test-python.sh

goauthentikAGENTS.md

authentik / website

goauthentik/authentik/website/AGENTS.md

tightly as possible for a true one-off: ` ` in Markdown/MDX (`// spellchecker:ignore ...` in code), or ` ` for a single line. Never disable the checker for a whole page. ## Deployment Deployment

rollupAGENTS.md

rollup

rollup/rollup/AGENTS.md

manually write the pull request in their own words to show they care. ## Code Review Focus - **Ignore style/linting issues** in test sample files (`test/*/samples/`) except for `_config.js` files - Test

vaporAGENTS.md

vapor

vapor/vapor/AGENTS.md

tools (Copilot, Claude, Cursor, etc.) to help write or refine code is fine, but a human must understand, review, and take responsibility for every change in the PR. - **Fully automated

zulipAGENTS.md

zulip

zulip/zulip/AGENTS.md

open-source community, with maintainers who have consistently emphasized **high standards for codebase readability, code review, commit discipline, debuggability, automated testing, tooling, documentation, and all the other subtle details that

EveryIncAGENTS.md

compound-engineering-plugin

EveryInc/compound-engineering-plugin/AGENTS.md

exception — they review the files, they don't re-read them for context. `ce-code-review`'s project-standards reviewer globs `CODING_STANDARDS.md`, the designated criteria source, and reads `CLAUDE.md`/`AGENTS.md

biomejsAGENTS.md

biome

biomejs/biome/AGENTS.md

After implementation, code generation, formatting, linting, and tests, review the complete change with [biome-code-review](./.agents/skills/biome-code-review/SKILL.md). - Use a fresh subagent when one is available. - Provide only the review scope

kieranklaassenAGENTS.md

compound-engineering-plugin

kieranklaassen/compound-engineering-plugin/AGENTS.md

exception — they review the files, they don't re-read them for context. `ce-code-review`'s project-standards reviewer globs `CODING_STANDARDS.md`, the designated criteria source, and reads `CLAUDE.md`/`AGENTS.md

ciliumAGENTS.md

cilium

cilium/cilium/AGENTS.md

strictly a manual step for the human author to confirm they have reviewed the changes. ### Coding and attribution Only human beings can ever be credited in commit messages. This means

clockworklabsAGENTS.md

SpacetimeDB

clockworklabs/SpacetimeDB/AGENTS.md

code follows the style doc or is moving toward it. Read the doc in full before your first edit here, and follow it. - No marker: Core. A person reviews every

activepiecesDeletes or force-pushesAGENTS.md

activepieces

activepieces/activepieces/AGENTS.md

surface needs the placeholder. ## Key Utilities (`@activepieces/shared`) `apId()`, `tryCatch()`, `tryCatchSync()`, `isNil()`, `spreadIfDefined()`, `spreadIfNotUndefined()`, `ActivepiecesError({ code, params })`, `SeekPage `, `formErrors`, `BaseModelSchema`, `chunk()`, `partition()`, `unique()`, `omit()`, `sanitizeObjectForPostgresql()` ## Testing ```bash npm run test-unit

No other project uses it yet