Severity tier for review comments#82
Open
dangng2004 wants to merge 1 commit into
Open
Conversation
Each comment now carries a "severity" field with values "minor", "moderate", or "major" alongside the existing technical/logical type. - models.py: new SEVERITY_VALUES constant and Comment.severity field; serialized in to_dict when set. - prompts.py: shared SEVERITY_RUBRIC injected into the deep-check, zero-shot, and zero-shot-chunk prompts; output schemas include the field. - utils.py: parse_comments_from_list normalizes the severity string and defaults to "moderate" when missing or invalid. - cli.py: severity propagated into the viz JSON output.
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.
Summary
Status
Draft. Functional but no tests or downstream consumers (e.g. ranking, filtering, viz UI styling) wired up yet.
Test plan