LeetTrack
approvedby Son Phan
Create organized LeetCode notes with auto-fetched metadata, smart topic categorization, and spaced repetition review tracking. - This plugin has not been manually reviewed by Obsidian staff.
Obsidian LeetTrack
[!NOTE] Disclaimer: This plugin is vibe coded โ built rapidly with AI assistance and creative energy rather than traditional software engineering rigor. It works well for my personal workflow, but expect rough edges. Use at your own risk, and feel free to open issues or contribute fixes!
Create organized LeetCode problem notes with auto-fetched metadata, smart topic categorization, and spaced repetition review tracking โ all inside your Obsidian vault.
Features
One-Click Problem Note Creation
Enter a LeetCode URL, Problem ID, or title slug โ the plugin fetches all metadata (title, difficulty, topic tags) from the LeetCode GraphQL API and creates a fully structured note.
Accepts any input format:
- Full URL:
https://leetcode.com/problems/trapping-rain-water/ - Problem ID:
42 - Title slug:
two-sum,3Sum
Smart Topic Categorization
Notes are automatically filed into topic folders matching the LeetCode Top Interview 150 roadmap:
| Folder | Topics |
|---|---|
01 - Array & String | Arrays, strings, in-place operations |
02 - Two Pointers | Two-pointer techniques |
03 - Sliding Window | Window-based problems |
04 - Matrix | 2D grid problems |
05 - Hashmap | Hash table lookups |
06 - Linked List | Singly/doubly linked lists |
07 - Stack | Stack, monotonic stack |
08 - Intervals | Interval merging/insertion |
09 - Binary Tree | Tree traversal, BST |
10 - Graph | BFS, DFS, graph theory |
11 - Trie & Search | Trie data structure |
12 - Backtracking | Combinatorial search |
13 - Binary Search | Search algorithms |
14 - Heap | Priority queue problems |
15 - Dynamic Programming | DP, memoization |
16 - Math & Bit | Math tricks, bit manipulation |
Problems not in the Top 150 are categorized by their LeetCode tags. You can also define custom topic mappings in settings.
Mastery & Spaced Repetition System
Track your learning progress with a three-level mastery system:
| Mastery | Meaning | Default Review Interval |
|---|---|---|
| ๐ด Red | Missed pattern or forgot logic | 1 day |
| ๐ก Yellow | Understood pattern but stumbled on code | 3 days |
| ๐ข Green | Solved quickly with clear understanding | 7 days |
The plugin manages the full learning lifecycle:
Import Problem โ Study / Solve โ Set Mastery
โ โ
Reschedule โ Update Mastery โ Review
Review scheduling is automatic โ when you update mastery, the next review date is calculated and stored in the note's frontmatter. The "Show Problems Due for Review" command lists all overdue problems.
You can also mark a problem as reviewed without changing its mastery level โ this bumps the review date forward based on the current mastery and increments the review count. Available as a command or via the โ button in the Due Reviews modal.
Batch Import
Import multiple problems at once. Paste a list of IDs, URLs, or slugs โ one per line โ and the plugin creates all notes with progress tracking and a summary showing imported/skipped/failed counts.
Auto-Updating Hub Dashboard
A living 00 - LeetCode Hub.md dashboard with:
- Due for Review โ problems requiring immediate attention
- Progress Overview โ mastery distribution (Red/Yellow/Green)
- Statistics โ study streak, solve counts, difficulty distribution
- Review Queue โ all Red and Yellow problems
- Mastered Problems โ your Green list
- Topic Breakdown โ categorized problem lists
LeetCode CN Support
Toggle between leetcode.com and leetcode.cn in settings for users in China.
Installation
Community Plugins (Recommended)
- Open Settings โ Community plugins โ Browse
- Search for "LeetTrack"
- Click Install, then Enable
Manual Installation
- Download
main.js,manifest.json, andstyles.cssfrom the latest release - Create a folder
<your-vault>/.obsidian/plugins/obsidian-leet-track/ - Copy the three files into that folder
- Restart Obsidian and enable the plugin in Settings โ Community plugins
BRAT (Beta Testing)
- Install the BRAT plugin
- Add beta plugin:
Chillaxhson/obsidian-leet-track
Usage
Commands
All commands are accessible via the Command Palette (Cmd/Ctrl + P):
| Command | Description |
|---|---|
| Create new problem note | Open the input modal to create a single problem note |
| Batch import problem notes | Import multiple problems at once |
| Refresh hub dashboard | Regenerate the dashboard from current vault state |
| Update problem mastery | Set mastery level (Red/Yellow/Green) for the active note |
| Show problems due for review | List all problems past their review date |
| Mark current problem as reviewed | Bump the review date without changing mastery |
The ribbon icon (code icon in the left sidebar) opens the Create new problem note modal.
Frontmatter
Each problem note includes structured YAML frontmatter:
---
difficulty: Medium
mastery: red
tags:
- leetcode-interview-150
- array
- two-pointers
created-date: 2026-08-28
review-date: 2026-08-29
review-count: 0
---
| Field | Description |
|---|---|
difficulty | Easy, Medium, or Hard |
mastery | red, yellow, or green |
tags | LeetCode topic tags + leetcode-interview-150 if applicable |
created-date | When the note was generated |
solved-date | When you first marked mastery (set automatically) |
review-date | Next scheduled review date |
review-count | Number of times you've reviewed this problem |
Settings
| Setting | Default | Description |
|---|---|---|
| LeetCode root folder | LeetCode | Relative path to your LeetCode notes directory |
| Dashboard filename | 00 - LeetCode Hub.md | Name of the hub dashboard file |
| Auto-update hub dashboard | true | Refresh dashboard when notes are created/updated |
| Include problem description | false | Fetch and embed the problem description (HTML โ Markdown) |
| Use LeetCode CN | false | Switch to leetcode.cn API and URLs |
| Default mastery (Easy) | green | Initial mastery for Easy problems |
| Default mastery (Med/Hard) | red | Initial mastery for Medium and Hard problems |
| Red interval | 1 day | Days until next review when mastery is Red |
| Yellow interval | 3 days | Days until next review when mastery is Yellow |
| Green interval | 7 days | Days until next review when mastery is Green |
| Custom topic mappings | {} | Override tag โ topic folder mappings |
FAQ
The LeetCode API request failed
The plugin uses the public LeetCode GraphQL API. If you get rate-limited (HTTP 429), the plugin will automatically retry with exponential backoff (up to 3 retries). If it still fails, wait a few minutes and try again.
Can I customize the note template?
Yes โ the template is stored in the plugin settings (accessible via data.json in your vault's plugin folder). Available template variables:
{{id}}, {{title}}, {{difficulty}}, {{mastery}}, {{tags}},
{{url}}, {{topicFolder}}, {{created-date}}, {{review-date}},
{{description}}, {{#description}}...{{/description}}
Does it work on mobile?
Yes. The plugin uses only Obsidian's built-in requestUrl API (no Node.js/Electron dependencies) and is marked isDesktopOnly: false.
I already have notes from the old LeetCode Helper plugin
The plugin automatically migrates legacy settings and reads both the old status field and the new mastery field from frontmatter.
Contributing
Development Setup
git clone https://github.com/Chillaxhson/obsidian-leet-track.git
cd obsidian-leet-track
npm install
npm run dev # Watch mode โ rebuilds on every save
Building for Production
npm run build # Type-check + minified production build
Project Structure
src/
โโโ main.ts # Plugin entry point
โโโ types.ts # All TypeScript interfaces
โโโ constants.ts # Top 150 map, topic logic
โโโ api/
โ โโโ leetcode.ts # GraphQL client with retry
โโโ services/
โ โโโ problem-service.ts # Note creation
โ โโโ review-service.ts # Mastery lifecycle
โ โโโ dashboard-service.ts # Hub dashboard
โโโ modals/
โ โโโ input-modal.ts # Single problem input
โ โโโ batch-import-modal.ts # Batch import
โ โโโ review-modal.ts # Mastery update
โโโ settings.ts # Settings tab + migration
โโโ utils/
โโโ parser.ts # HTML โ Markdown
โโโ date.ts # Review date calculations
License
MIT ยฉ Chillaxhson
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.