This is an automated email from the ASF dual-hosted git repository.

kaxil pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 34c96509ebc Move agent-assisted contribution docs out of the main 
README (#76951)
34c96509ebc is described below

commit 34c96509ebcb0e77aaf1066f754da8f7e86919da
Author: Kaxil Naik <[email protected]>
AuthorDate: Wed Nov 11 23:17:02 2026 +0000

    Move agent-assisted contribution docs out of the main README (#76951)
    
    The top-level README is for Airflow users, but its "Agent-assisted
    contribution (apache-magpie)" section is about installing maintainer
    PR-management and release skills. Move it unchanged to
    contributing-docs/33_agent_assisted_contribution.md, list it under
    Maintainer Tools in contributing-docs/README.rst, and point the links in
    AGENTS.md and the PR triage guide at the new page.
---
 AGENTS.md                                          |  4 +-
 README.md                                          | 42 ---------------
 contributing-docs/25_maintainer_pr_triage.md       |  2 +-
 .../33_agent_assisted_contribution.md              | 59 ++++++++++++++++++++++
 contributing-docs/README.rst                       |  3 ++
 5 files changed, 65 insertions(+), 45 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index ba72ee54f74..4d63c2a38c5 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -215,8 +215,8 @@ own agent harness. In Claude Code:
 its `verify-rc` skill verifies a release candidate and, per
 
[`.apache-magpie-overrides/release-verify-rc.md`](.apache-magpie-overrides/release-verify-rc.md),
 can test your own changes against a providers wave.
-The contributor-facing summary lives in the [Agent-assisted contribution
-section of `README.md`](README.md#agent-assisted-contribution-apache-magpie).
+The contributor-facing summary lives in
+[`contributing-docs/33_agent_assisted_contribution.md`](contributing-docs/33_agent_assisted_contribution.md).
 
 Airflow-specific modifications to framework-skill workflows live in
 [`.apache-magpie-overrides/`](.apache-magpie-overrides/) — the installed
diff --git a/README.md b/README.md
index 0c03cb40583..c55f0a34a0d 100644
--- a/README.md
+++ b/README.md
@@ -69,7 +69,6 @@ Use Airflow to author workflows (Dags) that orchestrate 
tasks. The Airflow sched
 - [Approach to dependencies of Airflow](#approach-to-dependencies-of-airflow)
 - [Contributing](#contributing)
 - [Community standards](#community-standards)
-- [Agent-assisted contribution 
(apache-magpie)](#agent-assisted-contribution-apache-magpie)
 - [Voting Policy](#voting-policy)
 - [Who uses Apache Airflow?](#who-uses-apache-airflow)
 - [Who maintains Apache Airflow?](#who-maintains-apache-airflow)
@@ -449,47 +448,6 @@ blocks and reporting accounts to GitHub — and how affected
 contributors can appeal a decision by emailing the PMC at
 `[email protected]`.
 
-## Agent-assisted contribution (apache-magpie)
-
-This repo uses the [`apache/magpie`](https://github.com/apache/magpie)
-framework, installed from its plugin marketplace. The framework provides
-maintainer-facing PR-management skills (`pr-management-triage`,
-`pr-management-code-review`, `pr-management-stats`, `pr-management-mentor`)
-that are exposed as agent skills in agent harnesses such as Claude Code.
-
-Nothing framework-related is committed to this repo, and a fresh clone
-needs no setup step — the plugin is installed per-user in your own agent
-harness. In Claude Code:
-
-```text
-/plugin marketplace add apache/magpie
-/plugin install magpie-pr-management@apache-magpie
-```
-
-Install `magpie@apache-magpie` instead to get every skill family at once,
-or add further families (`magpie-security`, `magpie-release-management`,
-…) one at a time. Pin a release rather than tracking `main` by adding the
-marketplace from a tag: `/plugin marketplace add apache/[email protected]`.
-
-The project's recommended set is recorded in `.apache-magpie.lock` and
-includes the release-management family, which lets an agent verify a
-release candidate — including an optional check that runs your own
-changes against a providers wave installed in Breeze:
-
-```text
-/plugin install magpie-release-management@apache-magpie
-```
-
-Other harnesses — Codex CLI, Gemini CLI, Copilot, Cursor — are covered in
-the framework's [marketplace
-guide](https://github.com/apache/magpie/blob/main/docs/setup/marketplaces.md).
-
-Airflow-specific modifications to framework workflows live in
-[`.apache-magpie-overrides/`](.apache-magpie-overrides/) (committed) —
-the installed plugin reads them at run time, so they apply to every
-contributor without anyone editing the framework. Framework changes go via
-PR to [`apache/magpie`](https://github.com/apache/magpie).
-
 <!-- START Who uses Apache Airflow, please keep comment here to allow auto 
update of PyPI readme.md -->
 
 ## Voting Policy
diff --git a/contributing-docs/25_maintainer_pr_triage.md 
b/contributing-docs/25_maintainer_pr_triage.md
index 17ec8edcb81..8302f0640af 100644
--- a/contributing-docs/25_maintainer_pr_triage.md
+++ b/contributing-docs/25_maintainer_pr_triage.md
@@ -107,7 +107,7 @@ alongside `pr-management-triage` is out of scope here.
 ## Stage 1: invoking the `pr-management-triage` skill
 
 The skill is provided by the 
[`apache/magpie`](https://github.com/apache/magpie) framework,
-installed from its plugin marketplace (see [`README.md` → "Agent-assisted 
contribution"](../README.md#agent-assisted-contribution-apache-magpie) for the 
install commands). Nothing is
+installed from its plugin marketplace (see [Agent-assisted 
contribution](33_agent_assisted_contribution.md) for the install commands). 
Nothing is
 committed to this repo, so the install is per-developer and one-off; 
afterwards Claude Code
 exposes the skill as `magpie-pr-management:pr-management-triage`. Its entry 
point is
 
[`SKILL.md`](https://github.com/apache/magpie/blob/main/plugins/magpie-pr-management/skills/pr-management-triage/SKILL.md);
 the rest of the directory breaks
diff --git a/contributing-docs/33_agent_assisted_contribution.md 
b/contributing-docs/33_agent_assisted_contribution.md
new file mode 100644
index 00000000000..9368a7cdd04
--- /dev/null
+++ b/contributing-docs/33_agent_assisted_contribution.md
@@ -0,0 +1,59 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+# Agent-assisted contribution (apache-magpie)
+
+This repo uses the [`apache/magpie`](https://github.com/apache/magpie)
+framework, installed from its plugin marketplace. The framework provides
+maintainer-facing PR-management skills (`pr-management-triage`,
+`pr-management-code-review`, `pr-management-stats`, `pr-management-mentor`)
+that are exposed as agent skills in agent harnesses such as Claude Code.
+
+Nothing framework-related is committed to this repo, and a fresh clone
+needs no setup step — the plugin is installed per-user in your own agent
+harness. In Claude Code:
+
+```text
+/plugin marketplace add apache/magpie
+/plugin install magpie-pr-management@apache-magpie
+```
+
+Install `magpie@apache-magpie` instead to get every skill family at once,
+or add further families (`magpie-security`, `magpie-release-management`,
+…) one at a time. Pin a release rather than tracking `main` by adding the
+marketplace from a tag: `/plugin marketplace add apache/[email protected]`.
+
+The project's recommended set is recorded in `.apache-magpie.lock` and
+includes the release-management family, which lets an agent verify a
+release candidate — including an optional check that runs your own
+changes against a providers wave installed in Breeze:
+
+```text
+/plugin install magpie-release-management@apache-magpie
+```
+
+Other harnesses — Codex CLI, Gemini CLI, Copilot, Cursor — are covered in
+the framework's [marketplace
+guide](https://github.com/apache/magpie/blob/main/docs/setup/marketplaces.md).
+
+Airflow-specific modifications to framework workflows live in
+[`.apache-magpie-overrides/`](../.apache-magpie-overrides/) (committed) —
+the installed plugin reads them at run time, so they apply to every
+contributor without anyone editing the framework. Framework changes go via
+PR to [`apache/magpie`](https://github.com/apache/magpie).
diff --git a/contributing-docs/README.rst b/contributing-docs/README.rst
index d28f71af172..5523c4c4565 100644
--- a/contributing-docs/README.rst
+++ b/contributing-docs/README.rst
@@ -160,6 +160,9 @@ Maintainer Tools
   open Pull Request queue (run deterministic quality checks, propose actions 
under explicit
   per-batch confirmation) and to surface backlog statistics by ``area:*`` 
label.
 
+* `Agent-assisted contribution <33_agent_assisted_contribution.md>`__ 
describes how to install the
+  ``apache/magpie`` agent skills used in this repository and where Airflow's 
overrides live.
+
 * `CLI Implementation Guide <27_cli_implementation_guide.rst>`__ describes 
where to implement new
   CLI features following AIP-94: remote commands go to ``airflowctl``, 
admin/deployment commands
   stay in the ``airflow`` CLI.

Reply via email to