DebugFlow

Debugging is often a fragmented process: developers reproduce an error, inspect a traceback, search through source code, determine the root cause, modify the code, and finally run tests to check whether the fix actually worked. DebugFlow brings these steps together into one guided debugging workflow. A developer starts by providing buggy Python code and its error or traceback. DebugFlow parses the traceback, analyzes the source code using Python AST analysis, identifies the affected function and line, and produces a structured root-cause explanation with a confidence score. The system then generates a proposed fix and presents the change as a reviewable diff. The original code is not silently modified—the developer explicitly decides whether to apply the proposed fix. Finally, DebugFlow executes the test suite in a controlled temporary workspace and reports whether the fix passes verification. The workflow is: Analyze → Identify Root Cause → Generate Fix → Review & Apply → Run Tests → Verify ### Key Features • Traceback parsing and error localization • Python AST-based source analysis • Structured root-cause diagnosis • Deterministic fix generation for supported error patterns • Human approval before applying changes • Automated pytest-based verification • Clear pass/fail results and workflow progress • React frontend with a FastAPI backend • Security-conscious execution using subprocess isolation controls and timeouts ### Technology Frontend: React, JavaScript, Vite, HTML, CSS Backend: Python, FastAPI Debugging Engine: Python AST, traceback analysis, pytest Development: IBM Bob IDE Repository: GitHub Deployment: Vercel + Render ### Why DebugFlow? DebugFlow is not simply an error-message generator. It is designed as a complete debugging workflow where diagnosis, proposed code changes, human review, and verification happen in sequence. The goal is to make debugging more structured and understandable, particularly for students, beginner developers, and small development teams. DebugFlow was developed as part of the IBM Bob 2.0 Hackathon, using IBM Bob as a core development tool throughout the project.