RoyLee1224 opened a new pull request, #73254: URL: https://github.com/apache/airflow/pull/73254
## Related dev list: https://lists.apache.org/thread/vggoo6yhx2x7nj6w0khc0ynwt9xrbrqq ## Why `AGENTS.md` is loaded for every task, but most contribution workflow guidance is only relevant when drafting or publishing a PR. Before this change, 314 lines / about 15.5 KB (42.3% of the root file) of detailed contribution workflow were loaded for every task. The root file was 537 lines / 36.6 KB, exceeding the 32 KiB project-document cap used in our Codex evaluation harness. This can leave trailing guidance unavailable to the agent. Claude Code also recommends keeping always-loaded project guidance under 200 lines. ## How - Reduce root `AGENTS.md` to universal repository guidance. - Move detailed contribution workflows into on-demand skills: - `airflow-pr-draft-summary` - `airflow-publish-changes` - Preserve a safe fallback: if the skills cannot be read, agents may draft or propose commands, but must not perform remote-changing actions. ## Evidence | | Before | After | Change | | --- | ---: | ---: | ---: | | Lines | 537 | 239 | -55.5% | | Root file size | 36.6 KB | 22.2 KB | -39.4% | - Leaves 10.6 KB below the 32 KiB harness cap. - `git diff --check` passes. - The contribution-workflow evaluation retained required behaviour with the relevant skill loaded. - Reusable eval cases and runner metadata will follow in a separate PR. <!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: https://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. For user-facing UI changes, please attach before/after screenshots (or a short screen recording) so reviewers can assess the visual impact. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- 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]
