MétaCan
Menu
Back to cohort
Record W4411950667 · doi:10.1109/forge66646.2025.00011

Automated Codebase Reconciliation using Large Language Models

2025· article· en· W4411950667 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldBiochemistry, Genetics and Molecular Biology
TopicMachine Learning in Bioinformatics
Canadian institutionsAdvanced Micro Devices (Canada)University of Toronto
Fundersnot available
KeywordsCodebaseComputer scienceProgramming languageSoftware

Abstract

fetched live from OpenAlex

Large-scale software projects frequently encounter the challenge of manually propagating code changes across branches—a process that is error-prone due to code divergence, conflicting dependencies, and branch-specific modifications. Automating code porting can streamline development workflows, accelerate development cycles, and improve team collaboration. However, achieving this automation presents significant hurdles, particularly in maintaining consistency and resolving conflicts during codebase integration. We propose a novel approach that integrates algorithmic analysis with artificial intelligence-driven code generation, leveraging multi-agent systems to automate the identification of porting requirements and the development of ‘context-aware’ modifications. Our comprehensive, end-to-end framework starts by extracting recent commits to evaluate divergence. It subsequently assesses the necessity for porting changes and employs large language model (LLM) based systems to generate adaptive code suggestions tailored to files exhibiting inconsistencies. Experimental results suggest a substantial decrease in manual work through pipeline-generated pull requests. Despite these promising outcomes, integrating LLMs into complex workflows presents challenges, such as handling intricate dependencies and ensuring alignment with a company’s software development issue tracking and change management systems. This paper explores the potential and limitations of LLMs in advancing automation within software engineering and suggests future directions for enhancing these models to achieve industry-grade reliability.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.860
Threshold uncertainty score0.311

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.009
GPT teacher head0.301
Teacher spread0.291 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Quick stats

Citations1
Published2025
Admission routes1
Has abstractyes

Explore more

Same topicMachine Learning in BioinformaticsFrench-language works237,207