Skip to content

Fix deep-interview ambiguityThreshold runtime loading#2194

Open
Yeachan-Heo wants to merge 1 commit intodevfrom
omc/issue-2192-deep-interview-threshold
Open

Fix deep-interview ambiguityThreshold runtime loading#2194
Yeachan-Heo wants to merge 1 commit intodevfrom
omc/issue-2192-deep-interview-threshold

Conversation

@Yeachan-Heo
Copy link
Copy Markdown
Owner

Summary

  • load omc.deepInterview.ambiguityThreshold from Claude settings when materializing the built-in deep-interview skill
  • inject the resolved threshold before the state-init instructions and use it in the startup announcement instead of hardcoded 20%
  • add a focused regression test for project-over-profile settings precedence and dynamic threshold rendering

Testing

  • npx vitest run src/__tests__/skills.test.ts -t "loads deep-interview ambiguityThreshold"
  • npx tsc --noEmit --pretty false
  • npx eslint src/features/builtin-skills/skills.ts src/__tests__/skills.test.ts

Closes #2192

Builtin deep-interview skill templates documented an ambiguityThreshold in Claude settings, but the runtime loader always rendered the default threshold and a hardcoded 20% announcement. This change reads the configured threshold during skill materialization, applies it before the state-init instructions, and updates the startup copy to reflect the loaded percentage.

Constraint: Keep the fix scoped to issue #2192 and avoid broad skill templating changes
Rejected: Add a generic skill variable-expansion system | wider blast radius than the issue requires
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: If additional deep-interview settings need runtime interpolation later, extend the deep-interview-specific loader path deliberately instead of broadening skill rendering by default
Tested: npx vitest run src/__tests__/skills.test.ts -t "loads deep-interview ambiguityThreshold"; npx tsc --noEmit --pretty false; npx eslint src/features/builtin-skills/skills.ts src/__tests__/skills.test.ts
Not-tested: Full Vitest suite
@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@github-actions github-actions bot added the size/M label Apr 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant