Add 'classify-provider-changes' breeze command for deterministic change classification#68215
Merged
Merged
Conversation
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
June 8, 2026 09:26
bugraoz93
approved these changes
Jun 8, 2026
bugraoz93
left a comment
bugraoz93
left a comment
Contributor
There was a problem hiding this comment.
Breeze docs check failing. Looks good :)
potiuk
force-pushed
the
classify-provider-changes-command
branch
from
June 14, 2026 01:47
a6639af to
be68c48
Compare
jscheffl
approved these changes
Jun 14, 2026
…ge classification Rules-first classifier (doc-only/test-only/Bump decided; Fix/Add etc. -> needs_llm) that replaces the random --non-interactive discovery the prepare-providers-documentation skill abused. Outputs JSON so the skill takes deterministic results as-is and only LLM-classifies needs_llm commits.
…ommand images The new classify-provider-changes command left --github-repository ungrouped, failing the check-all-params-in-groups static check, and the command-output images were not regenerated. Group the option and refresh the generated command images.
The new command had an output image but was not embedded in any Breeze .rst doc, so the update-breeze-cmd-output check failed. Add a section describing it in the provider release commands docs.
potiuk
force-pushed
the
classify-provider-changes-command
branch
from
June 17, 2026 11:24
be68c48 to
54e5d93
Compare
shahar1
approved these changes
Jun 17, 2026
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
breeze release-management classify-provider-changes— a deterministic, rules-first classifier for provider changelog changes, replacing the random--non-interactiverun theprepare-providers-documentationskill 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_llmflag), so an agent/skill takes the deterministic results as-is and only spends LLM calls on the genuinely ambiguous commits.docs/**/*.rstchangeddocumentationtests/**/example_dags/**changedskipBump(dependency bump)miscneeds_llmDeliberately conservative:
Fix …/Add …subjects are not auto-classified (an "Add …" can be a breaking change), so they come back asneeds_llm. Rule logic lives inclassify_change_deterministically(covered by unit tests).Skill update
.agents/skills/prepare-providers-documentation/SKILL.mdPhase 1 now calls this command (no more random answers to throw away), and Phase 3 only spawns sub-agents forneeds_llmcommits.Includes the new command image and unit tests for the rule function.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines