4 items
Push accepted LeetCode solutions straight to a GitHub repo, with your own notes attached. LeetCommit automatically pushes your Accepted LeetCode solutions to a GitHub repository you choose. How it works: Solve a problem on leetcode.com and hit Submit. The moment LeetCode marks it Accepted, LeetCommit shows a quick popup to add notes and complexity, then pushes your code straight to your repo. Wrong Answer, Runtime Error, and other non-Accepted results are ignored entirely. What gets pushed: - Your solution file, organized as easy/ medium/ hard/ by difficulty, in a folder per problem (e.g. easy/1-two-sum/python_v1.py) - A notes.md per problem with your written notes, time/space complexity, and a link back to the problem — newest entry first - A short metadata header on every solution file: pushed date, difficulty, and the runtime/memory LeetCode itself measured Resubmit the same problem later and it's saved as a new version (python_v2.py, python_v3.py, ...) — nothing gets overwritten. Solve it in a second language and it lands in the same problem folder alongside the first. Connecting your account: LeetCommit uses GitHub's own Device Flow to connect — no password or token to copy anywhere. You pick exactly one repository to grant access to, and the GitHub App only ever requests Contents: Read and write on that repo. Nothing else in your GitHub account is touched. No backend server, no analytics, no tracking. Your code and token go directly from your browser to GitHub's API and nowhere else.
Aug 15, 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.