Refactor skill extraction and integrate semantic search for ranking - #13
Merged
Conversation
…ching for reviewer recommendations
…ement local LLM skill extraction, and apply performance-based candidate truncation.
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.
This pull request introduces major improvements to the reviewer recommendation system by integrating a semantic code search (vector database) for commit diffs, optimizing skill extraction to minimize LLM usage, and adding a batch skill extraction tool powered by a local LLM. These changes enhance both the quality and efficiency of reviewer recommendations, reduce reliance on external LLM calls, and improve the maintainability and extensibility of the codebase.
Semantic Code Search and Reviewer Boosting:
Integrated a new vector database pipeline using Nomic's embedding model and Chroma to index and search commit diffs, enabling semantic retrieval of historically similar code changes. This is used to identify and boost potential reviewers with relevant prior experience. (
codience/src/Reviewer_Recommender/Data/commit_diff_vectordb.py,codience/src/Reviewer_Recommender/PRNew/Reviewer_Engine.py) [1] [2] [3] [4] [5]Reviewer candidates found via vector DB are now included in the candidate pool and receive a scoring boost proportional to the number of matching code chunks. Their matched code diffs are also shown in the LLM prompt for transparency. (
codience/src/Reviewer_Recommender/PRNew/Reviewer_Engine.py,codience/src/Reviewer_Recommender/PRNew/scorer_agent.py) [1] [2] [3]Skill Extraction Optimization:
codience/src/Reviewer_Recommender/PRNew/commit_history_utils.py) [1] [2] [3] [4] [5]Batch Skill Extraction Tool:
codience/src/Reviewer_Recommender/PRNew/batch_skill_extractor.py)Developer Experience and Codebase Cleanups:
codience/src/Reviewer_Recommender/PRNew/Reviewer_Engine.py,codience/src/Reviewer_Recommender/PRNew/commit_history_utils.py,codience/src/Reviewer_Recommender/PRNew/llm.py) [1] [2] [3].vscode/settings.jsonto set the default Python interpreter path for consistent development environments.These changes collectively make the reviewer recommendation system more intelligent, efficient, and easier to extend for future enhancements.