potiuk opened a new pull request, #68143:
URL: https://github.com/apache/airflow/pull/68143
Adopts the apache-steward #460 model — `.agents/skills/` as the single
canonical home for agent skills, with `.github/skills/` and
`.claude/skills/` carrying thin per-skill relay symlinks into it. This
makes every skill discoverable by the shared-path agent cluster (Codex,
Cursor, Gemini CLI, Copilot, OpenCode, …) alongside Claude Code and
GitHub, instead of being tied to `.github/skills/`.
What changed:
- Relocate the repo's own skills (`aip-user-stories`, `airflow-translations`,
`prepare-providers-documentation`) and the committed `magpie-setup`
bootstrap from `.github/skills/` to `.agents/skills/`, with relays from
`.github` and `.claude` (history preserved via git renames).
- Refresh the committed `magpie-setup` bootstrap from apache/airflow-steward
`main` (the #460 canonical-`.agents` model; `conventions.md` folded into
`agents.md`).
- Re-point the prek hooks and tooling that anchored on `.github/skills/...`
at the new `.agents/` location — license headers, blacken-docs, codespell,
inclusive-language, markdownlint, lychee, the translation-namespace sync
trigger, and the hardcoded path in `sync_translation_namespaces.py`. prek
skips symlinks, so only the real files (now under `.agents/`) are
processed.
- `.gitignore` negations so the `.claude/skills/` relays stay tracked, and a
provider-release doc path reference update.
No runtime/user-facing Airflow behaviour changes — this is agent-skills
plumbing and CI-config only.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 4.8 (1M context))
Generated-by: Claude Code (Opus 4.8 (1M context)) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
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]
