pith. sign in
Pith Number

pith:M5LOKMGP

pith:2026:M5LOKMGP6FHGYAWOSX23YLHQTS
not attested not anchored not stored refs resolved

Automated Root-Cause Subclassification and No-Code Fix Generation for Invalid Bug Reports

Emre Dinc, Eray Tuzun, Mahmut Furkan Gon, Tevfik Emre Sungur

Large language models with retrieval and agent techniques can subclassify root causes of invalid bug reports and generate no-code fixes.

arxiv:2605.17561 v1 · 2026-05-17 · cs.SE · cs.AI · cs.MA

Add to your LaTeX paper
\usepackage{pith}
\pithnumber{M5LOKMGP6FHGYAWOSX23YLHQTS}

Prints a linked badge after your title and injects PDF metadata. Compiles on arXiv. Learn more · Embed verified badge

Record completeness

1 Bitcoin timestamp
2 Internet Archive
3 Author claim open · sign in to claim
4 Citations open
5 Replications open
Portable graph bundle live · download bundle · merged state
The bundle contains the canonical record plus signed events. A mirror can host it anywhere and recompute the same current state with the deterministic merge algorithm.

Claims

C1strongest claim

Retrieval augmented generation achieves the highest overall performance with 0.66 weighted F1 for subclassification of invalid bug reports, while agentic web search achieves the highest overall Judge LLM success rate at 68.9% for no-code fix generation.

C2weakest assumption

The manually curated gold-standard benchmark accurately captures the distribution and labeling of invalid bug reports across real software projects and that the judge LLM evaluations align with human judgment of fix quality.

C3one line summary

RAG reaches 0.66 weighted F1 on invalid bug report subclassification while agentic web search reaches 68.9% judge success on no-code fix generation, using a new gold-standard benchmark.

References

61 extracted · 61 resolved · 7 Pith anchors

[1] The cost of poor software quality in the us: A 2022 report, 2022
[2] (2025) Jira software: Issue and project tracking tool 2025
[3] (2025) Github issues: Collaborative issue tracking platform 2025
[4] Chaff from the wheat: Characterizing and determining valid bug reports, 2020
[5] A data-driven approach for understanding invalid bug reports: An industrial case study, 2023

Formal links

2 machine-checked theorem links

Receipt and verification
First computed 2026-05-20T00:04:46.004490Z
Builder pith-number-builder-2026-05-17-v1
Signature Pith Ed25519 (pith-v1-2026-05) · public key
Schema pith-number/v1.0

Canonical hash

6756e530cff14e6c02ce95f5bc2cf09cbd74529bfd29e5cbd4eb28b5d8e3acbb

Aliases

arxiv: 2605.17561 · arxiv_version: 2605.17561v1 · doi: 10.48550/arxiv.2605.17561 · pith_short_12: M5LOKMGP6FHG · pith_short_16: M5LOKMGP6FHGYAWO · pith_short_8: M5LOKMGP
Agent API
Verify this Pith Number yourself
curl -sH 'Accept: application/ld+json' https://pith.science/pith/M5LOKMGP6FHGYAWOSX23YLHQTS \
  | jq -c '.canonical_record' \
  | python3 -c "import sys,json,hashlib; b=json.dumps(json.loads(sys.stdin.read()), sort_keys=True, separators=(',',':'), ensure_ascii=False).encode(); print(hashlib.sha256(b).hexdigest())"
# expect: 6756e530cff14e6c02ce95f5bc2cf09cbd74529bfd29e5cbd4eb28b5d8e3acbb
Canonical record JSON
{
  "metadata": {
    "abstract_canon_sha256": "2c87656401e1d2bb6ef3c6aa23d30ef10d86f2ca6af9035a6d04820ad9c5d51f",
    "cross_cats_sorted": [
      "cs.AI",
      "cs.MA"
    ],
    "license": "http://creativecommons.org/licenses/by/4.0/",
    "primary_cat": "cs.SE",
    "submitted_at": "2026-05-17T17:45:13Z",
    "title_canon_sha256": "27e08a3136ee2c5b59ef466e885e339e5464d65982514373f7f1246dd80b0a7f"
  },
  "schema_version": "1.0",
  "source": {
    "id": "2605.17561",
    "kind": "arxiv",
    "version": 1
  }
}