fix: improve repair feedback for LLM-as-a-Judge validations#1248
Open
akihikokuroda wants to merge 1 commit into
Open
fix: improve repair feedback for LLM-as-a-Judge validations#1248akihikokuroda wants to merge 1 commit into
akihikokuroda wants to merge 1 commit into
Conversation
Signed-off-by: Akihiko Kuroda <akihikokuroda2020@gmail.com>
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
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.
Pull Request
Issue
Fix: #1247
Description
When LLM-as-a-Judge validation returns binary yes/no answers, use the requirement
description as the repair reason instead of just 'yes' or 'no'. This applies to all
semantic validations (check(), req() without validation_fn, etc.) regardless of
check_only setting.
Previously, repair feedback would show:
Now it shows:
This makes repair feedback more actionable and helps models understand what needs
to be fixed during repair iterations in RepairTemplateStrategy and MultiTurnStrategy.
Testing
Attribution
Adding a new component, requirement, sampling strategy, or tool?
If your PR adds or modifies one of the types below, check the matching box. A checklist of type-specific review items will be posted as a comment.
NOTE: Please ensure you have an issue that has been acknowledged by a core contributor and routed you to open a pull request against this repository. Otherwise, please open an issue before continuing with this pull request.