fix(config): Inherit org execution defaults for repo skills - #514
Open
gricha wants to merge 1 commit into
Open
Conversation
Let repo-local skills inherit base agent, auxiliary, and synthesis defaults when omitted. Preserve explicit repo overrides across nested and legacy config fields. Keep policy defaults isolated. Co-Authored-By: GPT-5.6 Sol <noreply@anthropic.com>
gricha
marked this pull request as ready for review
August 22, 2026 04:54
![sentry-junior[bot]](https://avatars.githubusercontent.com/in/2960336?s=60&v=4){kind=small}
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
1 participant
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.
Let repo-local skills inherit agent, auxiliary, and synthesis execution defaults from the org base config when they omit them. This covers both the nested configuration and the legacy model, turn-limit, and auxiliary-retry fields.
Layered resolution currently isolates repo-local skills from these defaults. An omitted model can therefore fall through to the environment or SDK default even when the org base config selects a model. In production this allowed repo-local skills to run on K2.6 while the org security review ran on Grok.
Explicit repo settings retain precedence. Reporting thresholds, path filters, and other policy defaults remain layer-local, preserving the separation between org-enforced and repo-owned skills.
The alternative in getsentry/.github#211 sets a global model fallback. That covers an omitted primary model, but it cannot carry effort, turn limits, auxiliary settings, or synthesis settings and leaves the layered configuration behavior surprising.