AGENTS.md examples from real projects

gogsAGENTS.md

gogs

gogs/gogs/AGENTS.md

incompetent you are. Do it right on your first try, fact-check and review after changes. If you are not sure, ask for help. - When you see changes made outside

No other project uses it yet

momentAGENTS.md

moment

moment/moment/AGENTS.md

standalone runtime smoke test must remain executable on Node 8, and generated library code must continue to pass the runtime compatibility workflow. Moment has no runtime dependencies

No other project uses it yet

apacheAGENTS.md

airflow

apache/airflow/AGENTS.md

selected project in the monorepo with only dependencies that it has ## Security Model When reviewing code, writing security documentation, or performing security research, keep in mind the following aspects

apacheAGENTS.md

airflow / providers

apache/airflow/providers/AGENTS.md

When reviewing provider PRs Flag any of these patterns: - `**conn.extra_dejson` or `**self.extra_dejson` spread into a constructor or call. - Looping over `conn.extra_dejson.items()` and forwarding every key. - New code paths

No other project uses it yet

ogulcancelikAGENTS.md

herdr

ogulcancelik/herdr/AGENTS.md

already split into state, actions, and input. Keep it that way. - **Platform code is isolated.** OS-specific behavior lives in the matching `src/platform/ .rs` file, with only shared traits, types

siyuan-noteAGENTS.md

siyuan

siyuan-note/siyuan/AGENTS.md

major features, review applicable compliance requirements, licensing terms, privacy risks, and costs before technical design 2. **Check the premise and existing capabilities:** Inspect the relevant implementation, settings, code snippets, shortcuts

serverlessReads credentialsAGENTS.md

serverless

serverless/serverless/AGENTS.md

call sites. Keep `esbuild` listed in `external` in `packages/sf-core/esbuild.js` — bundling esbuild's own code breaks the worker it spawns (see the comment there). `packages/framework-dist` is an empty shell

cliAGENTS.md

cli

cli/cli/AGENTS.md

commit, push, or publish merely because implementation is complete. For PR review, use [code-review](.github/skills/code-review/SKILL.md). For authorized maintainer debt maintenance, use [tech-debt-burndown](.github/skills/tech-debt-burndown/SKILL.md). For terminal demonstration evidence

No other project uses it yet

DIYgodAGENTS.md

RSSHub

DIYgod/RSSHub/AGENTS.md

Review Comments**: Before requesting re-review, ensure all previous review comments are addressed, not just some of them. ### Code Organization 45. **Move Functions Up**: Move function definitions to the highest

No other project uses it yet

danny-avilaAGENTS.md

LibreChat

danny-avila/LibreChat/AGENTS.md

Keep only what the change carries, and describe the code as it stands rather than narrating earlier commits or review rounds. Naming the merged pull request that caused

files-communityAGENTS.md

Files

files-community/Files/AGENTS.md

changes, run the focused build that can prove it and report anything left unverified. ## Code Review Rules ### Native interop - Reject new uses of `DllImport`. Prefer existing interop wrappers or CsWin32

sickn33AGENTS.md

agentic-awesome-skills

sickn33/agentic-awesome-skills/AGENTS.md

Before PRs, run `npm run validate && npm run test && npm run security:docs`. ## Coding Style & Naming Conventions Use Markdown for skills and docs, JavaScript/Node for most tooling, and Python

No other project uses it yet

streamlitAGENTS.md

streamlit

streamlit/streamlit/AGENTS.md

short doc note, or leaving the code as is. Security issues and data loss still need a real fix. This applies to review feedback too: a reviewer, human

streamlitAGENTS.md

streamlit / agents

streamlit/streamlit/.claude/agents/AGENTS.md

review comments | | `qa-testing-feature` | QA test features using Playwright | | `reviewing-local-changes` | Code review for quality, security, best practices, and product/API alignment | | `simplifying-local-changes` | Simplify and refine code

streamlitAGENTS.md

streamlit / skills

streamlit/streamlit/.claude/skills/AGENTS.md

third person** in descriptions (e.g., "Validates code changes" not "I validate code changes") - **Keep file references one level deep** from SKILL.md - **Use sentence casing** for titles and headers - Capitalize only

streamlitAGENTS.md

streamlit / frontend

streamlit/streamlit/frontend/AGENTS.md

Data fetching without race protection (stale response can overwrite newer data). ### Rewrite patterns (preferred code) - Derived value during render: ```tsx // ❌ Avoid // const [fullName, setFullName] = useState("") // useEffect(() => setFullName(`${firstName} ${lastName}`), [firstName

No other project uses it yet

streamlitReads credentialsAGENTS.md

streamlit / workflows

streamlit/streamlit/.github/workflows/AGENTS.md

Description | |----------|---------|-------------| | `ai-pr-review.yml` | `ai-review`/`ai-final-review` label or manual | AI-powered code and product-alignment review using Cursor CLI | | `ai-qa-testing.yml` | `ai-qa-test` label or manual | AI-powered

streamlitAGENTS.md

streamlit / specs

streamlit/streamlit/specs/AGENTS.md

template 3. Create PR titled `[spec] Feature name` (keep in Draft until ready for review) ## Spec Guidelines ### Problem First, Solution Second Never start with what you want to build. Start

SentryAGENTS.md

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

ColorlibHQAGENTS.md

AdminLTE

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

No other project uses it yet