jason810496 commented on issue #62500: URL: https://github.com/apache/airflow/issues/62500#issuecomment-4028191936
Since we should keep the contribution guide up to date whenever we update the Breeze CLI or any CI/CD tooling anyway, using the contribution guide as the source of truth also makes sense to me. > One thing that is important in those workflows. NOT EVERYTHING should be done with breeze. This is also a good reason for not defining agent skills rules in Breeze, since if we mention tools outside of Breeze in the Breeze CLI docstring, it should be not straightforward to maintain. All of the above discussion and the diagram of the contributing workflow are correct and pretty much the same as what we do in our daily development. Great discussion! So the problem now is: What will the automated (or semi-automated) mechanism for transforming the contributing docs into Agent skills look like? And how do we maintain this automated mechanism? Since the Agent Skills should be much more concise than the contributing docs, they should be well structured (and may have a nested structure for “references”) as a rules-based guideline, with concrete examples/commands for the Agent to refer to. -- 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]
