jason810496 commented on issue #62500: URL: https://github.com/apache/airflow/issues/62500#issuecomment-4020631289
> [@jason810496](https://github.com/jason810496) [@potiuk](https://github.com/potiuk), I have few questions from the community before making a proposal, > > 1. How strongly do we want the Breeze CLI to remain the single source of truth for agent skills? Should the skills be entirely generated from CLI metadata, or should there be an intermediate schema describing workflows that Breeze commands map into? > 2. If Breeze CLI evolves, do maintainers expect the AI skill layer to adapt automatically through the prek sync mechanism, or should we maintain some backward compatibility layer for agents? The main question here is the long-term maintainability of the Airflow project itself. That’s why it would be better to have a single source of truth for agent skills, to avoid agent skills becoming outdated over time. It’s totally fine to have an intermediate schema for Breeze and agent skills, as long as we consider the long-term maintainability effort and make sure the mechanism itself is easy enough for maintainers to keep the agent skills synchronized with the Breeze CLI. For the second question, in most cases, Airflow contributors/maintainers will use the Breeze CLI directly installed from the `main` branch. The Breeze CLI supports the `--use-airflow-version` flag for some common commands. To sum up, the latest Breeze CLI itself should always be able to work with any Airflow version. We just need to make sure the mechanism is able to keep agent skills up to date with changes to the Breeze CLI -- or, more accurately, that changes to the Breeze CLI and changes to the agent skills are part of the same atomic Git commit history from my perspective. -- 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]
