Abhishekmishra2808 commented on issue #62500: URL: https://github.com/apache/airflow/issues/62500#issuecomment-4022487522
@jason810496 Thanks Looking at the Breeze structure, it seems feasible to derive the skill layer directly from the CLI definitions rather than maintaining a separate manually curated spec. A prek hook could generate the skill definitions from the Breeze command metadata and fail when the generated output diverges from the committed files. That would effectively enforce synchronization and ensure that any CLI change requires updating the corresponding agent skill in the same commit. This also keeps the Breeze CLI as the authoritative interface while allowing the skill layer to remain a thin, generated abstraction over it. One point I’m curious about: should the skill layer stay close to individual Breeze commands, or should it represent higher-level contributor workflows (e.g., static checks, targeted tests, environment transitions) that internally orchestrate multiple Breeze commands depending on context? -- 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]
