Vibe Debugger
Enhance GitHub Copilot with intelligent error analysis and clarifying questions.
Vibe Debugger enhances GitHub Copilot by providing intelligent error analysis and generating clarifying questions to improve code fix suggestions. It works seamlessly with Copilot to deliver more accurate and context-aware solutions.
Features
- Clarifying Questions: Generates targeted questions in clear, accessible language to understand error context
- Comprehensive Context Gathering: Collects code, imports, git changes, and other relevant information
- Enhanced Context for Copilot: Provides structured context to enable Copilot to generate more precise fixes
- Specialized Error Categories: Supports 11 distinct error types with tailored analysis approaches
- Seamless Integration: Operates without external API calls, working directly with existing Copilot installations
Requirements
- GitHub Copilot: Active subscription required
- Visual Studio Code: Version 1.109.0 or higher
- Supported Languages: JavaScript, TypeScript
- Internet Connection: Required for AI-powered features
Getting Started
Installation
- Ensure GitHub Copilot is installed and configured
- Install Vibe Debugger from the Visual Studio Marketplace
- Restart VS Code if necessary
- Begin using
@vibedebugger in the Copilot Chat interface
Usage
Basic Workflow
- Open a file containing errors in VS Code
- Access Copilot Chat (
Ctrl/Cmd+Shift+I)
- Enter:
@vibedebugger fix this error
- Respond to the generated clarifying question
- Allow Vibe Debugger to provide enhanced context
- Request
@copilot to generate a fix using the provided context
Example Interaction
User: @vibedebugger fix this error
Vibe Debugger: What type of error are you encountering?
User: A null reference error
Vibe Debugger: [Provides enhanced context for Copilot]
User: @copilot Please fix this null reference error using the context above
Chat Interface
Interact with Vibe Debugger through VS Code's integrated chat interface:
@vibedebugger I have a null reference error on line 25
@vibedebugger Help me debug this async function
@vibedebugger Why is my variable undefined?
The extension analyzes the current file context and generates targeted questions to facilitate effective debugging.
Demo
Explore Vibe Debugger's capabilities with the interactive demo:
- Open the Command Palette (
Ctrl+Shift+P / Cmd+Shift+P)
- Execute "Vibe Debugger: Run Demo"
- Select from available error scenarios:
- Null Reference Errors
- Async/Await Issues
- DOM Manipulation Errors
Configuration
Customize Vibe Debugger through VS Code settings (Ctrl+,):
| Setting |
Description |
Default |
vibedebugger.autoNotify |
Enable automatic error notifications |
true |
vibedebugger.notificationDelay |
Delay before showing notifications (seconds) |
10 |
vibedebugger.debugMode |
Enable detailed logging |
false |
vibedebugger.maxNotificationsPerHour |
Maximum notifications per hour |
5 |
How It Works
Vibe Debugger employs a systematic approach to error analysis:
- Error Detection: Monitors VS Code's diagnostic system for errors and warnings
- Context Analysis: Collects relevant code context, dependencies, and error details
- Question Generation: Creates targeted questions based on error type and code context
- Interactive Guidance: Facilitates step-by-step debugging assistance
- Skill Development: Promotes independent debugging capabilities through guided learning
Known Issues
- Complex error patterns may require additional context
- Performance may vary with very large files
- Some advanced debugging scenarios require manual intervention
Support
Contributing
Contributions are welcome. Please refer to the Contributing Guide for detailed information.
📄 License
This extension is licensed under the MIT License.
Enhance your debugging workflow with AI-powered assistance.
Developed for the developer community.
