2 items
Automatically sync accepted LeetCode solutions to a polished GitHub repository. LeetBridge automatically saves your accepted LeetCode solutions to a GitHub repository you choose. Focus on solving problems while LeetBridge keeps your code organized and your solution index up to date. Build a browsable record of your practice without manually copying code, creating folders, or writing README entries after every submission. What LeetBridge does: - Automatically syncs accepted LeetCode submissions to GitHub. - Captures the submitted source code, programming language, problem title, number, and difficulty. - Organizes solutions into clearly named problem folders. - Generates per-problem READMEs and a repository-wide solution index. - Displays difficulty totals, a difficulty breakdown chart, and a language summary in your repository README. - Imports previous accepted solutions, selecting the latest accepted submission for each problem and language. - Prevents duplicate syncing using submission IDs. - Rebuilds your repository README from existing solution folders. - Lets you pause automatic syncing and control README updates from the popup. Getting started is simple: 1. Create a dedicated GitHub repository for your solutions. 2. Connect GitHub through LeetBridge and grant access to your chosen repository. 3. Open a LeetCode problem and submit a solution. 4. Accepted solutions are saved automatically. No local Git installation, manual token copying, or code configuration is required. You stay in control. GitHub authorization uses a GitHub App that you can restrict to a selected repository. Submitted code is sent directly from your browser to GitHub, with no developer-operated backend, advertising, or analytics. You can disconnect LeetBridge or revoke its access through GitHub at any time. A LeetCode account and a GitHub account are required. LeetBridge is an independent project and is not affiliated with, endorsed by, or sponsored by LeetCode or GitHub.
Sep 3, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.