You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/05/03 17:41:20 UTC
[PR] feat(skills): hook every framework skill into override-consultation protocol [airflow-steward]
potiuk opened a new pull request, #39:
URL: https://github.com/apache/airflow-steward/pull/39
## Summary
Wire every existing framework skill into the agentic-override protocol that landed in #38. Each of the 15 framework skills (excluding `setup-steward` itself) now carries an `## Adopter overrides` section that opts the skill into the run-time consultation pattern.
## What changed in each skill
A standard block was inserted right before the first `##` section (after the detail-files table where present, before `## Golden rules` / `## Inputs` / `## Prerequisites`):
```markdown
## Adopter overrides
Before running the default behaviour documented below, this
skill consults
[`.apache-steward-overrides/<skill-name>.md`](../../../docs/setup/agentic-overrides.md)
in the adopter repo if it exists, and applies any
agent-readable overrides it finds. See
[`docs/setup/agentic-overrides.md`](../../../docs/setup/agentic-overrides.md)
for the contract — what overrides may contain, hard rules,
the reconciliation flow on framework upgrade, upstreaming
guidance.
**Hard rule**: agents NEVER modify the snapshot under
`<adopter-repo>/.apache-steward/`. Local modifications go in
the override file. Framework changes go via PR to
`apache/airflow-steward`.
```
The bracketed link target carries the specific skill's name (e.g. `pr-management-triage.md` for the `pr-management-triage` skill), so adopter overrides land in the right file by convention.
## Skills updated (15)
| Setup family | Security family | PR-management family |
|---|---|---|
| `setup-isolated-setup-install` | `security-issue-import` | `pr-management-code-review` |
| `setup-isolated-setup-update` | `security-issue-import-from-md` | `pr-management-stats` |
| `setup-isolated-setup-verify` | `security-issue-import-from-pr` | `pr-management-triage` |
| `setup-shared-config-sync` | `security-issue-invalidate` | |
| | `security-issue-sync` | |
| | `security-cve-allocate` | |
| | `security-issue-deduplicate` | |
| | `security-issue-fix` | |
**Not updated**: `setup-steward` — it is the bootstrap that *manages* the override mechanism. Overriding it would create a chicken-and-egg loop.
## Test plan
- [x] All `prek run --all-files` hooks pass (markdownlint, typos, doctoc, check-placeholders)
- [x] Every framework skill except `setup-steward` has the `## Adopter overrides` section (visual grep)
- [x] Each section's link target carries the correct per-skill filename
- [ ] Reviewer eyeballs the wording for tone consistency across all 15 skills
- [ ] CI link-check (lychee) passes
## Out of scope
- Framework-skill content actually applying override files at run-time. The framework's skills are agentic markdown; the hook is a documented convention, not a runtime injector. The contract is: a skill that has the `## Adopter overrides` section commits to consulting the file. Future tooling (e.g. a sentinel pre-flight check or a hooks-from-skills mechanism) can enforce mechanically; for now, the convention is binding via the published contract.
- The `apache/airflow` re-adoption using the new mechanism (PR-C) — separate PR after this lands.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(skills): hook every framework skill into override-consultation protocol [airflow-steward]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #39:
URL: https://github.com/apache/airflow-steward/pull/39
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org