You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "choo121600 (via GitHub)" <gi...@apache.org> on 2026/05/11 08:30:31 UTC
[PR] skills/setup-override-upstream: trim frontmatter to fit metadata budget [airflow-steward]
choo121600 opened a new pull request, #128:
URL: https://github.com/apache/airflow-steward/pull/128
## Summary
Trims `setup-override-upstream` frontmatter (`description` + `when_to_use`) from **1,096 → 892** characters.
Same principle as #103 and the rest of #118's audit pass: frontmatter is the routing layer. The body covers the generalisability test, the design-decision example list, and the pre-commit step.
Tracking: #118
## Before / after
| | before | after | Δ |
|--------------|-------:|------:|-------:|
| description | 736 | 532 | -204 |
| when_to_use | 360 | 360 | 0 |
| **total** | **1,096** | **892** | **-204** |
| budget margin | 440 | 644 | +204 |
| budget | 1,536 | 1,536 | |
`when_to_use` is untouched — every line is either a literal trigger phrase or a routing skip cue (*"typically after running the override locally for a while"*) and has to stay verbatim.
## What moved where
| Detail | Where it lives now |
|---------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|
| `(some overrides encode project-specific decisions and should stay local)` (rationale parenthetical) | Body's generalisability discussion |
| `(configurable parameter, optional step, changed default, etc.)` (abstraction-example list) | Body's design-decision section |
| `runs the framework's pre-commit` (implementation detail) | Body Walk-through / standard project workflow |
The post-merge override-removal flow (*"After the PR merges and the adopter runs `/setup-steward upgrade`, the override file is no longer needed and the skill prompts for its removal"*) is **kept** in the frontmatter — it is the only routing signal that tells the agent this skill cleans up after itself.
## Trigger-phrase preservation
Every literal trigger phrase from the original `when_to_use` is preserved verbatim:
- `"upstream my override"`
- `"promote this override to the framework"`
- `"convert my local modification into a steward feature"`
- `"make this override a framework feature"`
- `"open a PR to apache-steward for this override"`
Routing skip cue preserved:
- *"typically after running the override locally for a while and deciding the change is worth contributing back"*
Routing recall does not regress.
--
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] skills/setup-override-upstream: trim frontmatter to fit metadata budget [airflow-steward]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #128:
URL: https://github.com/apache/airflow-steward/pull/128
--
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