potiuk opened a new pull request, #72673:
URL: https://github.com/apache/airflow/pull/72673
Airflow adopted apache-magpie through its snapshot mechanism: contributors
ran
`/magpie-setup` to fetch a gitignored snapshot pinned by
`.apache-magpie.lock`,
and to make that bootstrap possible the repo committed a `magpie-setup` skill
into `.agents/skills/`, `.claude/skills/` and `.github/skills/`.
The framework now ships a plugin marketplace, so agent harnesses install and
update it per-user. Nothing magpie-related needs to be committed here any
more,
and a fresh clone needs no setup step before the PR-management skills are
invocable:
```text
/plugin marketplace add apache/magpie
/plugin install magpie-pr-management@apache-magpie
```
What changes:
- Drop `.apache-magpie.lock`, the committed `magpie-setup` skill and its two
relay symlinks, and the twelve `.gitignore` rules that supported the
snapshot.
- Drop five now-dead `^\.agents/skills/magpie-setup/` excludes from
`.pre-commit-config.yaml`.
- Rewrite the install guidance in `README.md`, `AGENTS.md` and
`contributing-docs/25_maintainer_pr_triage.md`.
- Fix twelve links in the triage guide that pointed at
`/blob/main/.claude/skills/…` in the framework repo. That layout is gone —
the skills now live under
`/blob/main/plugins/magpie-pr-management/skills/…`.
All six targets verified to resolve.
`.apache-magpie-overrides/` is deliberately kept: the installed plugin reads
it
at run time, so Airflow's triage CI-check map and comment templates keep
applying to everyone.
Docs-and-tooling only, so no newsfragment.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Opus 5 (1M context)
Generated-by: Claude Opus 5 (1M context) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01HALJXR27XUFAKof5BFs5rR
--
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]
