LeetCommit
Push accepted LeetCode solutions to GitHub.
Install from the Chrome Web Store
Overview
When LeetCode marks a submission Accepted, LeetCommit opens a modal so you can add notes and Big-O, then commits the solution to a repository you choose.
Wrong answers never trigger a push. The code that lands in your repo is the exact submission LeetCode judged.
Repository layout
Solutions are organized by difficulty and problem number. Resubmits write a new version instead of overwriting.
Each problem folder keeps a notes.md with dated entries (newest first), including time and space complexity when you provide them.
How it works
- Connect GitHub once via device flow and grant the app access to a single repository.
- On
leetcode.com, LeetCommit watches LeetCode’s submit and check network calls. - Only an Accepted result (
status_code === 10) opens the push modal. - The extension commits the solution file and updates
notes.mdthrough the GitHub Contents API.
If you skip a push, the toolbar popup keeps the submission pending until you push or discard it.
Install
Chrome Web Store
- Install LeetCommit.
- Open the toolbar popup.
- Connect GitHub, then select a repository.
From source
- Clone this repository.
- Open
chrome://extensions, enable Developer mode, and choose Load unpacked. - Select the project folder, then connect GitHub from the popup.
Tech stack
| Layer | Details |
|---|---|
| Extension | Chrome Manifest V3, plain JavaScript, no build step |
| Detection | MAIN-world network interception on LeetCode submit/check |
| UI | Isolated-world content script modal |
| Auth | GitHub App device flow, with token refresh |
| API | GitHub Contents API via a background service worker |
Privacy
LeetCommit runs locally in your browser. Your code and GitHub token are sent only to GitHub’s API for the repository you authorize. See PRIVACY.md for the full policy.