cloudflare-os
cloudflare/cloudflare-os/AGENTS.md
kernel**: it defines the architecture and is held to a higher bar than UI/gatekeeper code. Reviewers read *every line* of `workshop-backend` and of API changes in `workshop-shared
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
cloudflare/cloudflare-os/AGENTS.md
kernel**: it defines the architecture and is held to a higher bar than UI/gatekeeper code. Reviewers read *every line* of `workshop-backend` and of API changes in `workshop-shared
github/codeql/unified/AGENTS.md
hand; regenerate it with `scripts/regenerate-node-types.sh` after changing the pinned swift-syntax version, then review the diff alongside the mapping in `extractor/src/languages/swift/swift.rs`. ## AST Mapping - The target AST shape is described
open-gsd/gsd-core/docs/AGENTS.md
agents** detailed in this section. Thirteen additional shipped agents (pattern-mapper, debug-session-manager, code-reviewer, code-fixer, ai-researcher, domain-researcher, eval-planner, eval-auditor, framework-selector, intel-updater
awslabs/mcp/src/dynamodb-mcp-server/AGENTS.md
Commit with conventional commit format (commitizen is configured) 6. Submit pull request or create code review ### Commit Message Format Follow [Conventional Commits](https://www.conventionalcommits.org/): ``` [optional scope]: [optional body] [optional
NVIDIA/garak/AGENTS.md
thread. ### 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
ibelick/ui-skills/AGENTS.md
headings. - Keep headings `font-medium` with `tracking-tight` where appropriate. - Use `JetBrains Mono` for code, commands, and monospace UI. - Keep labels and link text in sentence case. - Prefer light borders
openstatusHQ/openstatus/AGENTS.md
reasoning from the code alone. - When debugging a failure, start from the incident or issue Polylane recorded: it carries the evidence an investigation already gathered. - Polylane reviews pull requests
MervinPraison/PraisonAI/AGENTS.md
packages plus the TypeScript SDK: core protocols in `praisonaiagents/`, agentic terminal CLI in `praisonai-code/`, bots/gateway in `praisonai-bot/`, LLM fine-tuning + agent training in `praisonai-train/`, browser automation
backnotprop/plannotator/AGENTS.md
ExitPlanMode` via hooks, letting users approve or request changes with annotated feedback. Also provides code review for git diffs and annotation of arbitrary markdown files. > **Reusing the document UI (theme
cloudflare/vinext/AGENTS.md
bash git clone --depth 1 --single-branch --branch canary https://github.com/vercel/next.js.git .nextjs-ref ``` --- ## Code Style & Dependencies ### Prefer Node.js Built-in APIs Always use Node.js built-in modules and APIs
google/adk-go/AGENTS.md
session, or hand the diff to a subagent that did not write the code. An agent reviewing work it produced in the same session re-reads its own intent rather
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
cloudflare/workerd/AGENTS.md
upstream code. These patches are stored in the `patches/` directory and are applied during the build process. When updating these dependencies, it's important to review and update the corresponding
cloudflare/workerd/src/workerd/api/streams/AGENTS.md
become dangling See `README.md` §Safety Pattern Catalog for detailed When/Why/How for each pattern. ## CODE REVIEW RULE When reviewing changes to streams code, check whether the change requires updates
cloudflare/workerd/src/workerd/jsg/AGENTS.md
unvisited fields across the codebase, enforcing invariants 1 and 2 at build time. ## CODE REVIEW RULE When reviewing changes to JSG code, check whether the change requires updates
apify/apify-mcp-server/AGENTS.md
handle similar cases. Ask: "Am I adding code, or fixing the code that's already there?" - **Self-review your diff.** Before declaring done, review: Is this the minimal
freecodexyz/free-code/AGENTS.md
MUST** review every stored reference and asynchronous callback for lifetime, every resource for one clear owner, and every interface for explicit copy/move/ borrow semantics. - **MUST NOT** approve code merely because
mongodb/mongo-go-driver/AGENTS.md
AGENTS.md This file provides guidance to AI agents when working with code in this repository. ## Project Official MongoDB Go Driver (`go.mongodb.org/mongo-driver/v2`). Correctness, backward compatibility, and conformance to [MongoDB Driver
strands-agents/harness-sdk/AGENTS.md
writer`, `pr-feedback`), docs (`docs-writer`, `docs-reviewer`, `docs-audit`, `docs-planner`), and code review (`strands-review`). See [`.agents/skills/README.md`](./.agents/skills/README.md) for what each does and when
strands-agents/harness-sdk/site/AGENTS.md
work", "what docs need writing" | When authoring or reviewing documentation pages, follow the voice guide and the terminology lock. When verifying code examples in docs, follow the tiered procedure
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.