I built CodeBlitz as a Chrome extension for practicing LeetCode interviews with Gemini. It reads the problem from the page and runs the practice interview in a sidebar. The repository is also listed on my github profile page.
CodeBlitz is a Chrome extension that adds an AI mock interviewer to LeetCode. It reads the problem on the page and uses Gemini to run a practice interview in a sidebar, favoring hints over full solutions.
In Interview mode, CodeBlitz asks one concise question at a time, prefers hints over answers, and shows a session timer.
In Mentor mode, CodeBlitz gives general guidance and returns code when you ask for it.
CodeBlitz sends the problem statement from the page to Gemini as context.
I can dictate answers using the Web Speech API in CodeBlitz.
CodeBlitz keeps chat history for each problem in Chrome storage.
CodeBlitz has one-click prompts to explain the problem, show an example, or define key terms.
The adjustable sidebar lets me resize or collapse it, and it remembers my layout.
CodeBlitz uses React, TypeScript, Vite, tsup, Chrome Extension Manifest V3, and the Gemini API.
The content script, codeblitz/src/contentScript.ts, adds the sidebar to LeetCode and reads the problem.
The background service worker, codeblitz/src/background.ts, calls Gemini, with a 25-second timeout, retries, and model fallback.
The popup, codeblitz/src/App.tsx, shows the current problem and starts an interview.
I need Node.js and a Gemini API key to set up CodeBlitz.
The setup commands are `cd codeblitz; npm install; cp .env.example .env; npm run build:all`. After copying the environment file, I add my key to `.env`.
- To load CodeBlitz in Chrome, I open
chrome://extensions, enable Developer mode, load unpackedcodeblitz/dist, then start AI Interview on a LeetCode problem.
The build scripts use the Windows copy command; I should replace the Windows copy command with cp in package.json on macOS or Linux.
The API key is written into the built extension; setup is for local use only and builds containing the key should not be published or shared.
The .env file and the generated scripts in public/ are ignored by Git.
For distribution, I should move Gemini calls to a backend so the key stays on a server.