potiuk opened a new pull request, #68215:
URL: https://github.com/apache/airflow/pull/68215

   Adds `breeze release-management classify-provider-changes` — a 
**deterministic, rules-first** classifier for provider changelog changes, 
replacing the random `--non-interactive` run the 
`prepare-providers-documentation` skill abused purely for discovery.
   
   ### What it does
   For each provider with unreleased changes, it classifies every commit with 
hard-coded, high-confidence rules and outputs JSON (discovery + classification 
+ a `needs_llm` flag), so an agent/skill takes the deterministic results as-is 
and only spends LLM calls on the genuinely ambiguous commits.
   
   | Rule | → |
   |---|---|
   | only `docs/**/*.rst` changed | `documentation` |
   | only `tests/**` / `example_dags/**` changed | `skip` |
   | subject starts `Bump ` (dependency bump) | `misc` |
   | everything else | `needs_llm` |
   
   Deliberately conservative: `Fix …` / `Add …` subjects are **not** 
auto-classified (an "Add …" can be a breaking change), so they come back as 
`needs_llm`. Rule logic lives in `classify_change_deterministically` (covered 
by unit tests).
   
   ### Skill update
   `.agents/skills/prepare-providers-documentation/SKILL.md` Phase 1 now calls 
this command (no more random answers to throw away), and Phase 3 only spawns 
sub-agents for `needs_llm` commits.
   
   Includes the new command image and unit tests for the rule function.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.8)
   
   Generated-by: Claude Code (Opus 4.8) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


-- 
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]

Reply via email to