TagDebt: A Bot to Support Technical Debt Management

• URL: http://arxiv.org/abs/2605.29869v1
• Date: Thu, 28 May 2026 12:54:10 GMT
• Title: TagDebt: A Bot to Support Technical Debt Management
• Abstract summary: We present and evaluate TagDebt, a bot that can be integrated within GitHub repositories and automatically assign labels to issues.<n>We carried out a Design Science Research study to design and implement TagDebt.<n>We interviewed 16 practitioners to check the bot's usefulness, ease of use, and contextual factors that might impact the bot's usage.
• Score: 4.547720478540521
• License: http://creativecommons.org/licenses/by/4.0/
• Abstract: Context: Technical debt (TD) is a widely studied metaphor that helps to explain how sub-optimal decisions that can harm software maintainability over time. Although incurring TD is not intrinsically bad, tracking and managing TD are crucial to avoid its negative effects. Hence, researchers and practitioners have proposed and developed diverse approaches and tools for managing TD. However, we are still lacking specialized tools for technical debt management (TDM), specifically ones that can be easily integrated into existing development workflows. Objective: We present and evaluate TagDebt, a bot that can be integrated within GitHub repositories and automatically assign labels to issues (i.e., SATD or non-SATD). TagDebt helps in the identification of TD (i.e., by looking for self-admitted technical debt (SATD)), leading to more efficient TDM. Methods: We carried out a Design Science Research study to design and implement TagDebt. For its evaluation, we executed a Technology Acceptance Model (TAM) study through interviews with 16 practitioners, to check the bot's usefulness, ease of use, and contextual factors that might impact the bot's usage (such as team size and practitioners' roles). Results: Overall, practitioners found that TagDebt is useful, especially for organizing issues and reducing manual work. Furthermore, they pointed out that the bot is overall easy to use, and its documentation is clear. The analysis also revealed that contextual factors, such as team and codebase size, impact the decision to adopt TagDebt. Finally, several improvements were suggested, such as including features to check and update the source code. Conclusion: TagDebt is a proof-of-concept for the development and usage of more specialized tools for TDM. It helps to make TD visible without disrupting existing workflows and help practitioners avoid the risks of unmanaged TD.

Related papers

• Offloading Score: Measuring AI Reliance Through Counterfactual Workflows [70.84727355516559]
  We introduce offloading score, a measure of reliance that quantifies the fraction of cognitive effort offloaded to an AI tool.<n>We validate offloading score through intrinsic evaluations of metric validity, and a controlled user study.<n>We show that offloading score detects significantly higher reliance in time-constrained settings.
  arXiv  Detail & Related papers  (2026-05-28T05:44:31Z)
• LLMs Improving LLMs: Agentic Discovery for Test-Time Scaling [63.679448814185456]
  Test-time scaling (TTS) has become an effective approach for improving large language model performance.<n>Existing TTS strategies are largely hand-crafted: researchers design patterns and tune them by intuition, leaving much of the computation-allocation space unexplored.<n>We propose an environment-driven framework, AutoTTS, that changes what researchers design: from individual TTSs to environments where TTS strategies can be discovered automatically.
  arXiv  Detail & Related papers  (2026-05-08T17:59:40Z)
• A Practical Guide for Establishing a Technical Debt Management Process (Preprint) [0.9685837672183747]
  Technical Debt (TD) refers to short-term beneficial software solutions that impede future changes.<n>We conducted 19 workshops and retrospectives, analyzing 108 meetings (96 hours) over a 30-month period.<n>We identified the TDM approaches used by all teams as a starting point for best practices.
  arXiv  Detail & Related papers  (2026-03-03T15:28:50Z)
• Establishing Technical Debt Management -- A Five-Step Workshop Approach and an Action Research Study [1.3514953384460018]
  Technical debt (TD) items are constructs in a software system providing short-term benefits but hindering future changes.<n>This study aimed to establish a TDM process in an IT company based on a workshop concept.
  arXiv  Detail & Related papers  (2025-08-21T13:44:01Z)
• Managing Technical Debt in a Multidisciplinary Data Intensive Software Team: an Observational Case Study [12.110862907227203]
  There is an increase in the investment and development of data-intensive (DI) solutions.<n>Without careful management, this growing investment will also grow associated technical debt (TD)<n>This research contributes empirical, practice based insights about multidisciplinary DI team TD management practices.
  arXiv  Detail & Related papers  (2025-06-23T00:53:45Z)
• Automating Technical Debt Management: Insights from Practitioner Discussions in Stack Exchange [2.964027141453931]
  Technical debt management (TDM) is essential for maintaining long-term software projects.<n>The adoption of tools remains low, indicating the need for further research on TDM automation.<n>This study aims at understanding which TDM activities practitioners are discussing with respect to automation in TDM, what tools they report for automating TDM, and the challenges they face that require automation solutions.
  arXiv  Detail & Related papers  (2025-02-05T13:23:44Z)
• Detection of Technical Debt in Java Source Code [12.07607688189035]
  Technical debt (TD) describes the additional costs that emerge when developers opt for a quick and easy solution to a problem.<n>In this study, through the analysis of comments and their source code from 974 Java projects, we curated the first ever dataset of TD identified by code comments.
  arXiv  Detail & Related papers  (2024-11-08T10:12:33Z)
• ActiveAD: Planning-Oriented Active Learning for End-to-End Autonomous Driving [96.92499034935466]
  End-to-end differentiable learning for autonomous driving has recently become a prominent paradigm. One main bottleneck lies in its voracious appetite for high-quality labeled data. We propose a planning-oriented active learning method which progressively annotates part of collected raw data.
  arXiv  Detail & Related papers  (2024-03-05T11:39:07Z)
• CONCORD: Clone-aware Contrastive Learning for Source Code [64.51161487524436]
  Self-supervised pre-training has gained traction for learning generic code representations valuable for many downstream SE tasks. We argue that it is also essential to factor in how developers code day-to-day for general-purpose representation learning. In particular, we propose CONCORD, a self-supervised, contrastive learning strategy to place benign clones closer in the representation space while moving deviants further apart.
  arXiv  Detail & Related papers  (2023-06-05T20:39:08Z)
• Learning Instructions with Unlabeled Data for Zero-Shot Cross-Task Generalization [68.91386402390403]
  We propose Unlabeled Data Augmented Instruction Tuning (UDIT) to take better advantage of the instructions during instruction learning. We conduct extensive experiments to show UDIT's effectiveness in various scenarios of tasks and datasets.
  arXiv  Detail & Related papers  (2022-10-17T15:25:24Z)
• TubeTK: Adopting Tubes to Track Multi-Object in a One-Step Training Model [51.14840210957289]
  Multi-object tracking is a fundamental vision problem that has been studied for a long time. Despite the success of Tracking by Detection (TBD), this two-step method is too complicated to train in an end-to-end manner. We propose a concise end-to-end model TubeTK which only needs one step training by introducing the bounding-tube" to indicate temporal-spatial locations of objects in a short video clip.
  arXiv  Detail & Related papers  (2020-06-10T06:45:05Z)

This list is automatically generated from the titles and abstracts of the papers in this site.

This site does not guarantee the quality of this site (including all information) and is not responsible for any consequences.