Platform to programmatically author, schedule and monitor workflows.
Airflow's file ranges from repository structure and commands to writing and contribution policy. It defines one domain term, classifies security reports, explains newsfragments, fixes remote names, and limits commit trailers.
├── ├── · symlink → AGENTS.md ├── .github │ └── instructions │ └── ├── airflow-core │ ├── docs │ │ └── security │ │ ├── │ │ └── │ └── src │ └── airflow │ ├── _shared │ │ └── │ ├── api_fastapi │ │ └── execution_api │ │ └── │ └── ui │ └── ├── airflow-ctl │ └── ├── contributing-docs │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ └── ├── dev │ ├── breeze │ │ └── doc │ │ ├── adr │ │ │ └── │ │ └── ci │ │ └── │ ├── ide_setup │ │ └── │ ├── │ ├── │ └── ├── providers │ ├── <provider> │ │ └── docs │ │ └── changelog.rst — the changed provider's changelog │ ├── common │ │ └── ai │ │ └── │ ├── elasticsearch │ │ └── │ ├── opensearch │ │ └── │ └── ├── registry │ ├── │ └── · symlink → AGENTS.md ├── scripts │ └── ci │ └── prek │ └── ├── task-sdk │ └── src │ └── airflow │ └── sdk │ ├── _shared │ │ └── · symlink → ../../../../../airflow-core/src/airflow/_shared/AGENTS.md │ └── execution_time │ └── schema │ └── └──
01 / House vocabulary
The term uses title case in prose. Literal code tokens keep their original spelling, including inside fenced blocks, and anti-pattern quotes may show the wrong form when teaching the rule.
Source excerpt starting at line 8.Write **Dag** (title case) in all prose. Keep the all-caps or lowercasespelling only when reproducing a literal code token — never rewrite these,even inside fenced code blocks:
02
The guide separates security findings into vulnerabilities, known limitations, and deployment hardening. It links the security model, including the chapter that defines what is not a vulnerability.
03 / Contribution etiquette
Known fixes go straight to a pull request to avoid duplicate work. Deferred fixes still need an issue that outlives the workaround.
Source excerpt starting at line 368.- Open issues attract drive-by submissions, often from other agents, that haven't seen the in-flight work. That produces duplicate fixes, low-quality
04
Create a tracking issue before finalizing a workaround, version cap, or partial fix. Cite its number in the pull request and place the full URL beside the code.
05 / Hard prohibitions
Agents may not add themselves as co-authors. A separate pull-request field records the agent's name and version.
Source excerpt starting at line 210.- NEVER add Co-Authored-By with yourself as co-author of the commit. Agents cannot be authors, humans can be, Agents are assistants.
06
Before remote commands, run git remote -v. If the two expected names differ, report the mismatch and propose the exact rename commands.
07
Tests are to cover exactly what the PR changes: every changed behavior gets a test, every test must fail without the change, and tests for pre-existing logic or third-party functions are excluded.
Source excerpt starting at line 152.- Target exactly 100% coverage of what the PR changes — no more, no less. Every changed or added behaviour must have a test; every test must fail without the PR's change. Do not add tests for pre-existing logic that was already present before the PR, and do not test standard-library or third-party functions. The exception is deliberate behaviour or integration tests, which may cross those boundaries by design.
These instructions explain how to work in Airflow. Modem shows your agents what customers said, who is affected, and what changed.
