cuml / cpp
NVIDIA/cuml/cpp/agents.md
Code Review Guidelines - cuML C++/CUDA **Role**: Act as a principal engineer with 10+ years experience in GPU computing and high-performance numerical computing. Focus ONLY on CRITICAL and HIGH
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
NVIDIA/cuml/cpp/agents.md
Code Review Guidelines - cuML C++/CUDA **Role**: Act as a principal engineer with 10+ years experience in GPU computing and high-performance numerical computing. Focus ONLY on CRITICAL and HIGH
NVIDIA/cuml/python/agents.md
Code Review Guidelines - cuML Python **Role**: Act as a principal engineer with 10+ years experience in machine learning systems and Python API design. Focus ONLY on CRITICAL and HIGH issues
elastic/elasticsearch-js/AGENTS.md
generate a contribution is not contributing. PRs opened this way will be closed without review. If a human asks you to "find something to work on" or points
cloudflare/cloudflare-docs/AGENTS.md
task, read `.flue/AGENTS.md` first.** That file covers the worker architecture, workflow routing, specialist agents (code review, conventions, style-guide), R2 state management, local dev scripts, and deployment. All bot-related
cloudflare/cloudflare-docs/.flue/AGENTS.md
than resolving them. A failed judge publishes filtered specialist findings as unverified. ### Routing | Specialist | Reviews | | ------------- | ----------------------------------------------------------------------------------------------- | | `code` | Every added line of non-MDX files, and added lines inside code blocks
microsoft/SynapseML/AGENTS.md
narrowest relevant repository skill: [Scala changes](.github/skills/scala-code/SKILL.md), [local setup](.github/skills/synapseml-local-setup/SKILL.md), and [code review](.github/skills/code-review/SKILL.md). 4. For requests to make one or more issues or PRs "5/5", "200% ready", or merge
github/gh-aw/AGENTS.md
intent - Workflow create/update/debug/upgrade tasks → `.github/skills/agentic-workflows/SKILL.md` - Core engineering conventions, validation flow, and command playbooks → `.github/skills/developer/SKILL.md` - Code organization, file structure, WASM stubs, string patterns → `.github/skills/developer-code-organization/SKILL.md` - Security best practices, template injection, shell script
iflytek/skillhub/AGENTS.md
enum. Follow the design doc's intent for new code. **Key transitions:** - Normal user first upload → `PENDING_REVIEW` (no initial DRAFT) - SUPER_ADMIN first upload → `PUBLISHED` (direct publish) - Review approve
aipoch/open-science/AGENTS.md
React adapter. Put a key in `common` only when its UI meaning and reviewed translation are the same in both processes; an identical English key is not enough. The guard
SaladDay/cc-switch-cli/AGENTS.md
issues. - Validate every finding against the code. Make minimal fixes for confirmed issues within scope, run the relevant checks, then start another blind review with a new subagent under
tiann/hapi/AGENTS.md
passing checks when code, dependencies, and environment are unchanged; commit/push/PR transitions alone do not require reruns. Run repository-wide checks when explicitly requested as well. - Review this task's changes
TabularisDB/tabularis/AGENTS.md
symbols, 25156 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely. > Index stale? Run `node .gitnexus/run.cjs analyze` from the project root
clidey/whodb/AGENTS.md
source of truth for Codex, Claude Code via import, opencode, Pi, and other compatible coding agents. - Use `.agents/README.md` as the index for deeper agent guidance, and read only the relevant
mistralai/mistral-vibe/client-e2e/AGENTS.md
timing in those snapshot tests, it will always fail - The tests should be completely code agnostic - The tests should concsist of scenarios with just a list of events - user bytes
mistralai/mistral-vibe/vibe/cli-rust/AGENTS.md
paulvezia/rewrite_rust branch, always create a worktree and fix the code there - No unit tests allowed in rust files !! ## First MVP - We need basic conversation working, same UI, all other features
Waishnav/devspace/AGENTS.md
workflow to file the PR and `babysit-pr` to monitor CI and reviews. ## Where code lives - `src/server.ts` — MCP server setup, tool registration, and response wiring. - `src/workspaces.ts` — workspace lifecycle, instructions, skills
NVIDIA/Model-Optimizer/AGENTS.md
feedback - **Judge each comment on its merits before acting.** Check it against the current code — reviewers comment on stale diffs, and bot findings (CodeRabbit, Claude) are claims to verify
qixing-jk/all-api-hub/AGENTS.md
nvmrc`, and hooks. ## Project boundaries - Keep `src/entrypoints/**` thin; feature UI belongs in `src/features/**`. Shared code must not import options-page entrypoints. Keep React state ownership outside `src/services
awslabs/aidlc-workflows/AGENTS.md
recording, exact stage-rule delivery, forwarding-loop enforcement, reviewer read-scope enforcement, review-receipt write-freeze enforcement, code-generation plan-approval enforcement, direct state-transition enforcement, and token-usage folding
homeassistant-ai/ha-mcp/AGENTS.md
policy and controls](docs/agents/issue-intake.md) for source handling, maintainer overrides, permissions, and bench validation. ### Automated Code Review After every push, inspect human and automated feedback. Codex and CodeRabbit findings are hypotheses
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.