C++ Diagnostic

C++ Diagnostic The Problem: C++ compiler errors are often technically accurate but difficult to understand in context. Messages such as “was not declared in this scope,” “cannot convert,” or “expected ';'” tell developers what the compiler detected, but not necessarily why it happened or what they should check next. This is especially challenging for students, beginners, and developers working with unfamiliar code. Our Solution: Context Diagnostic is a developer tool that converts raw C++ compiler diagnostics into concise, contextual, and actionable explanations. It combines compiler messages with relevant source-code context and uses a two-layer diagnostic system. First, a deterministic diagnostic engine identifies known error patterns such as missing semicolons, undefined variables, type mismatches, incorrect arguments, and missing includes. These errors are handled locally, providing fast and predictable explanations without requiring AI. For unknown or complex errors, the system can use an AI fallback through OpenRouter. The AI receives the compiler diagnostic and relevant source context and generates a developer-friendly explanation, likely cause, evidence, and suggested checks. Target Users: The primary users are C++ students, beginner developers, and developers debugging unfamiliar code. Through the VS Code extension, users receive explanations directly inside their coding environment instead of manually copying compiler errors and source code into another tool. What Makes It Unique: Context Diagnostic is not simply an AI chatbot for code. Its key innovation is combining compiler-grounded deterministic analysis with contextual AI fallback. C++ Code → Compiler → Diagnostic + Source Context → Deterministic Analysis → Known Error: Instant Diagnosis / Unknown Error: AI Analysis → Unified Diagnosis → VS Code This approach is efficient because common errors are resolved immediately without AI latency or unnecessary API usage, while complex errors can still benefit from AI reasoning. The system also treats source evidence as an important part of diagnosis. It connects explanations to the relevant source line and includes safeguards against mismatches between compiler-reported locations and the actual source. Ultimately, Context Diagnostic bridges the gap between a compiler’s technical error message and a developer’s actual debugging needs—explaining not only what went wrong, but also where to look and what to check next, directly within the development workflow.