arXiv (All)
open access
Detecting Incorrect LLM Explanations for Automated Program Repair
LLM-generated explanations help developers understand automated program repair (APR) rationale and assess patch quality. Incorrect explanations can mislead developers about a repair's reliability, making their detection important. However, manually inspecting the growing volume of generated repairs
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Detecting Incorrect LLM Explanations for Automated Program Repair#1483088
- How Do LLMs Read Bug Reports? An Empirical Study of Attention in LLMs for Automated Program Repair#411126
- Externalizing Requirement-to-Repair Artifacts as Observable Traces for LLM-Based Program Repair#1084819
- Externalizing Requirement-to-Repair Artifacts as Observable Traces for LLM-Based Program Repair#919493
- Does More Thinking Pay Off? Reasoning Cost and Correctness of LLMs in Code Generation and Bug Fixing#1473672
Record · ID 1489103
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive