⚡ fixr — Autonomous Zero-Config Code Debugger

fixr is the world's first Zero-Config AI debugger for the terminal. Once installed globally via NPM, it automatically executes your code, captures the error stream, analyzes the exact problem, and sends it to an LLM to generate an English explanation and an exact fix. No API keys, no configuration, and no complicated commands required.

🚀 Getting Started (Beginner Guide)

Prerequisites

Before you begin, make sure you have Node.js installed on your system.

1. Install Globally (One-time only)

Open your terminal and run the following command to make the fixr command available across all your folders:

npm install -g fixr-zero-config

(The -g flag means "global", installing the tool directly to your system so you can use it anywhere).

2. Prepare Your Project (If needed)

If you are starting a brand new Node.js project, make sure to initialize your directory first to create a package.json file:

npm init -y

(Skip this step if you are debugging a Python, C++, or Java file, or if your project already exists).

3. That's it!

You are now ready to debug any file or project. You do NOT need to provide an API key—it is already built into the tool for you.

🛠 Complete Command Guide

🔍 1. The "Zero-Config" Full Project Scan

If you just downloaded a project or want to find architectural errors across all your files, you don't need to specify a file. Just type fixr inside your project folder.

fixr

• What it does: It automatically looks at every file in the folder, ignores node_modules, scans for bugs, and provides an AI summary of any missing packages or syntax errors.

⚡ 2. Debugging a Single File

If you are working on a specific file (like app.js or main.py) and it crashes, tell fixr to run it.

fixr app.js

• What it does: It runs the file behind the scenes. If there is an error (like a typo or crashed server), it captures the exact error and provides a clean, human-readable terminal output.

🧠 3. Deep AI Explanation (--ai)

If you get a complicated error and don't understand why it's happening, you can ask the AI for a deep explanation.

fixr app.js --ai

• What it does: It provides a highly detailed AI report in the terminal. It breaks down the Root Cause, explains it in simple English, and provides exact step-by-step instructions (and code snippets) on how to manually fix the issue.

✨ 4. The Magic Auto-Fix (--fix)

This is the most powerful command. If you don't want to fix the code manually, the AI will rewrite the broken file for you.

fixr app.js --fix

• What it does: It reads the broken code, sends it to the AI, and automatically overwrites the file with exactly correct, working code. The underlying issue is resolved instantly.

⚙️ Advanced Commands (Optional)

If you want to use your own OpenRouter API key or a specific LLM model (like Claude, Gemini, or GPT-4 instead of the free default), you can pass these flags:

• Override the default AI model:

fixr app.js --model openai/gpt-4o

• Use a custom API Key:

fixr app.js --key "sk-or-your-custom-api-key"

🏗 Why fixr is different?

1. Zero-Config: No .env files, no API keys, no setup. It just works.
2. Autonomous Detection: It doesn't just wait for you to tell it where the error is. Running fixr scans your entire project structure to find issues you might have missed.
3. React & Large Project Support: It understands complex folder structures and can identify errors in multiple files at once.
4. English-Only, Clear Results: Designed for humans. Every error is explained simply with a direct link to a fix or a missing package.

🌐 Supported Languages

| Language | Extension | Engine | | :--- | :--- | :--- | | JavaScript / Node / React | .js, .jsx, .ts, .tsx, .mjs | Node.js | | Python | .py | Python 3 | | C / C++ | .c, .cpp | GCC / G++ | | Java | .java | JDK |

👤 Author

Kamlesh Chandela

• 📧 Email: [email protected]
• 🐙 GitHub: @kamleshchandela

📄 License

MIT Licensed. Built with ❤️ for developers.