Repository navigation
Ask agents to measure performance-sensitive components - #74579
Merged
shahar1 merged 3 commits intoOct 18, 2026
Merged
Conversation
The publish skill's pre-push review now lists the components that run for every task, Task SDK call, log line or scheduler loop, and asks for a before/after measurement against the base commit, with a control, when a diff touches one of them.
Dev-iL
reviewed
Oct 12, 2026
Co-authored-by: Dev-iL <6509619+Dev-iL@users.noreply.github.com>
1 task done
Keep the component names in step 7 so the agent knows when to read the reference, and load the table and measuring steps only when needed.
shahar1
approved these changes
Oct 18, 2026
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
3 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.
First step toward #74562: until the micro-benchmark suite proposed there lands, this asks agents to measure performance-sensitive paths themselves, so AI-assisted changes do not skip it. Suggested in the contributors Slack.
The pre-push review of the
airflow-publish-changesskill gets a new step and a "Performance-sensitive components" section:timeitor the existingperf_kithelpers,assert_queries_countfor database code;Only the skill changes, not
AGENTS.md, so the skill-eval hash stays as it is. Once #74562 is in, the section can point at thebenchmarks/folders instead.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5.5) following the guidelines