feat(prompt): add clarification strategy for ambiguous user questions #677
+143
−32
Conversation
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
- Add clarification check as step 2 in SQL generation process - Add clarification-policy rule with must-clarify and should-clarify triggers - Add few-shot examples for clarification scenarios: - Ambiguous field names - Missing aggregation dimensions - Unclear filter conditions - Overly broad questions - User questions about SQL meaning - Enforce JSON response format for all scenarios including clarifications - Use complex 3-table schema in examples (sales_order, product, customer) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.
Summary
Changes
backend/templates/template.yaml中的 prompt 模板，添加澄清策略规则和示例