4 items
Save accepted LeetCode solutions to GitHub with a persistent queue and contest-safe local vault. SolveLog keeps your solved coding problems from disappearing into submission history. After LeetCode confirms an Accepted submission, SolveLog saves your code and problem metadata to a GitHub repository selected by you. Solutions are organised by topic, difficulty, and problem so that your practice becomes a searchable revision archive. KEY FEATURES • Automatically detects accepted LeetCode submissions • Organises solutions by topic → difficulty → problem • Uses a persistent, sequential queue for reliable GitHub commits • Prevents duplicate commits when the same problem is submitted repeatedly • Supports manual saving and download-only use • Includes Contest Safe Mode • Stores contest solutions locally until you choose to release them • Supports light, dark, and colourful pixel-inspired themes • Preserves queued submissions across browser restarts • Uses no advertising or analytics PRIVACY-FIRST GITHUB ACCESS SolveLog does not require access to every repository in your GitHub account. You can create a fine-grained GitHub token restricted to: • One selected repository • Contents: Read and write • No other repository permissions The token is stored locally in your browser and is sent only to GitHub's API when synchronising your solutions. CONTEST SAFE MODE When SolveLog detects a contest route, accepted solutions stay inside a local Contest Vault. They are not committed publicly until you review and release them. FREE AND OPEN SOURCE The free edition of SolveLog is available under the MIT License. Source code, tests, architecture documentation, and release history are publicly available on GitHub. SolveLog is not affiliated with or endorsed by LeetCode or GitHub.
Jul 31, 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.