gsemet commented on issue #62500: URL: https://github.com/apache/airflow/issues/62500#issuecomment-4286952595
Hello, Airflow is not particular. Every project have to deal with this "Agent does not really understand the specificities to my project". The only thing you need to focus is AGENTS.md - keep it short, mostly a map of the key reference document to read **with load instructions** - put in top the main entrypoints to build/test - declare your quality gates (scripts that needs to run when a tasks is finished) I usually split the AGENTS.md into 2: - AGENTS.md with how the project works, what are the main stack, main commands, really really short - a CONSTITUTION.md, pointed by AGENTS.md, with what the agent needs to know to do any modification of the project (commit, bug fix,...) - potentially external guidelines documents if the CONSTITUTION.md grows too much. - You can point to your skill in AGENTS.md, explaining when to load it, but same, keep it modular. You might want 1 skill for generic modification, and several skills (or progressive disclosed document in this skill) for some specific domains. Also, when i see: `Run a single test: uv run --project <PROJECT> pytest path/to/test.py::TestClass::test_method -xvs` => you might want to provide an easily to use launcher like justfile, this is way easier (and agents knows how to to `just --list` to list all available commands, and they can take parameters). mise-en-place is great as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
