Skip to content

Make .agents/skills the canonical agent-skills home#68143

Merged
potiuk merged 1 commit into
apache:mainfrom
potiuk:agents-skills-canonical
Jun 7, 2026
Merged

Make .agents/skills the canonical agent-skills home#68143
potiuk merged 1 commit into
apache:mainfrom
potiuk:agents-skills-canonical

Conversation

@potiuk
Copy link
Copy Markdown
Member

@potiuk potiuk commented Jun 6, 2026

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 Fix issue #459 - mysql error 2014 #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?
  • Yes — Claude Code (Opus 4.8 (1M context))

Generated-by: Claude Code (Opus 4.8 (1M context)) following the guidelines

Adopt the apache-steward apache#460 "canonical .agents/skills, relay other
agents into it" model and move every agent skill — the repo's own and
the magpie framework ones — to a single canonical home so they are
discoverable by the whole shared-path agent cluster (Codex, Cursor,
Gemini CLI, Copilot, OpenCode, …) alongside Claude Code and GitHub:

- `.agents/skills/<skill>` is the canonical entry; `.github/skills/`
  and `.claude/skills/` carry per-skill relay symlinks pointing into it.
- Relocate the repo's own skills (`aip-user-stories`,
  `airflow-translations`, `prepare-providers-documentation`) and the
  committed `magpie-setup` bootstrap copy from `.github/skills/` to
  `.agents/skills/`, with relays from `.github`/`.claude`.
- Refresh the committed `magpie-setup` bootstrap from
  apache/airflow-steward main (the apache#460 canonical-.agents model;
  `conventions.md` merged into `agents.md`).

Re-point the prek hooks and tooling that anchored on `.github/skills/...`
at the new `.agents/` location — full/short license headers,
blacken-docs, codespell, inclusive-language, markdownlint, lychee, the
translation-namespace sync trigger, and the hardcoded SKILL.md path in
`sync_translation_namespaces.py`. prek skips symlinks, so only the real
files (now under `.agents/`) are processed. Add `.gitignore` negations
so the `.claude/skills/` relays stay tracked, and update the
provider-release doc path reference.
@potiuk potiuk force-pushed the agents-skills-canonical branch from 37e0ffe to 5f2548e Compare June 6, 2026 20:42
@potiuk
Copy link
Copy Markdown
Member Author

potiuk commented Jun 7, 2026

Flaky tests fixed elsewhere.

@potiuk potiuk merged commit 942de38 into apache:main Jun 7, 2026
141 of 143 checks passed
@potiuk potiuk deleted the agents-skills-canonical branch June 7, 2026 08:07
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 7, 2026

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-2-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 942de38 v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants