6 items
Auto-document accepted HackerRank solutions to GitHub with free AI complexity analysis and interview notes. PrepPush automatically saves your accepted HackerRank solutions to your own GitHub repository with optional AI-generated interview prep notes. HOW IT WORKS 1. Solve a problem on HackerRank and click Submit Code (not Run Code). 2. When your submission is accepted, PrepPush captures it. 3. Your solution is pushed to GitHub, organized by language, difficulty, and problem name. 4. Optional: Gemini adds technique, time/space complexity, insight, interview talk-track, and pitfalls in the file header (omitted when unsure — empty beats wrong). WHAT YOU GET ON GITHUB • Folder layout: solutions/{language}/{difficulty}/{problem-slug}/solution-approachN.{ext} • File header includes a direct HackerRank problem link, difficulty, and AI notes (when enabled) • Multiple approaches on the same problem get approach2, approach3, etc. • Same logic re-submitted updates the same file (no duplicate spam) ONE-TIME SETUP • GitHub personal access token (classic, repo scope) • Optional: free Google Gemini API key for AI analysis • Keys are stored locally in Chrome on your device; PrepPush does not host your code or keys FEATURES • Works on hackerrank.com, including contest / prep-kit pages • Auto-saves your settings when you paste your token or API key • Light/dark popup theme • Open commits on GitHub from the popup REQUIREMENTS • Google Chrome • Your own GitHub token and (optional) Gemini API key PrepPush is an independent tool and is not affiliated with HackerRank, GitHub, or Google.
Jul 30, 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.