Abhishekmishra2808 commented on issue #62500:
URL: https://github.com/apache/airflow/issues/62500#issuecomment-4030087400
I see the motivation behind extracting the workflow structure directly from
"CONTRIBUTING.rst", but I’m a bit concerned about relying on parsing
documentation as the primary mechanism for generating agent skills.
Even with lightweight markers, documentation tends to evolve in ways that
are optimized for readability rather than strict structure. Over time this can
make parsing brittle, especially if formatting or section structure changes.
This is something a number of documentation-driven systems have run into when
automation depends too heavily on the layout of the docs.
My inclination would be to keep the contributing guide as the human-facing
source of truth for explaining the workflow, but generate the agent skills from
a small structured representation that the docs reference rather than directly
parsing the documentation itself. That keeps the documentation readable while
ensuring the agent-facing structure remains deterministic and easier to
validate.
Conceptually the flow would look something like:
Contributing Docs
│
▼
Workflow Definitions (structured)
│
▼
Generator
│
▼
Agent Skill Definitions
In that setup the docs still define and explain the workflow for
contributors, but the structured layer avoids coupling the automation to the
documentation format itself. It also makes validation easier as the workflow
schema can be enforced directly rather than inferred from doc structure.
--
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]
