Stop Letting Your // TODO Comments Go to Die

We’ve all been there. You’re deep in the zone, you spot a bug that isn't quite related to what you're doing, and you do the classic move:
// TODO: Fix this before the whole thing explodes.
Then you forget about it. Your teammates never see it. Six months later, the "explosion" happens, and you find that comment sitting there like a ghost. In most teams, // TODO comments are just a graveyard for good intentions.
Last week, I got fed up. I gave myself a 7-day challenge to build a tool that actually rescues these comments. I call it TeamSync TODO. It’s a VS Code extension that grabs your comments and sends them straight to a shared dashboard using Supabase.
The Idea & The Tech
I wanted to keep it simple. No fancy project management software—just a way to make code comments "talk" to the rest of the team.
VS Code API: To read the code.
Supabase: My favorite "shortcut." It handled my database and the real-time updates so the dashboard stays fresh without hitting refresh.
Carbon Design: A UI kit that makes everything look clean and professional without me having to be a "designer."
How the Week Went
The Start: Fighting with Regex
The first two days were a bit of a struggle. I had to write the logic that "scans" your code to find the comments. If you’ve ever worked with Regex, you know the pain. One wrong character and suddenly the extension thinks your entire file is one giant TODO.
The Middle: The "It Works!" Moment
By day 4, I got Supabase connected. I remember typing a comment in VS Code, hitting save, and watching a little card pop up on my web dashboard instantly. That was the "Aha!" moment. No more manual syncing or "hey, did you see my comment in auth.ts?"
The End: Cleaning Up
The last few days were all about DX (Developer Experience). I didn't want this to be a chore to use, so I made sure it stayed out of the way. It’s built to be fast, light, and actually helpful.
Want to try it? Here is the setup.
I wanted to make sure any dev could get this running in five minutes.
1. The Database
Just hop into your Supabase dashboard and run this SQL to create your tables. It’s pretty standard stuff—just columns for the description, who is assigned to it, and how urgent it is.
-- Create the teams table
CREATE TABLE teams (
id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
team_code TEXT UNIQUE NOT NULL,
team_name TEXT,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()
);
-- Create the todos table with priority checks
CREATE TABLE todos (
id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
team_id UUID REFERENCES teams(id) ON DELETE CASCADE,
assignee_email TEXT NOT NULL,
description TEXT NOT NULL,
priority INTEGER CHECK (priority IN (1, 2, 3)),
status TEXT CHECK (status IN ('open', 'closed')) DEFAULT 'open',
file_path TEXT,
line_number INTEGER,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()
);
CREATE INDEX idx_todos_team_id ON todos(team_id);
CREATE INDEX idx_todos_status ON todos(status);
2. Connect Your Editor
Install the extension.
Go to your VS Code settings and paste in your Supabase URL and Key.
Run the command
TeamSync: Configure Teamto give your group a name.
3. Start Tagging
Now, just write comments like this: // TODO 1: Fix the broken login button@varunm@gmail.com
The 1 is the priority (1 is high, 3 is low). The @ is for your teammate's email. When you're ready, just run TeamSync: Sync TODOs from the command palette. Boom. Your team can now see exactly what needs to be fixed and where it is.
Does this actually help?
The goal wasn't to replace tools like Jira. The goal was to catch the small stuff that usually falls through the cracks. It's about keeping the "technical debt" visible so it doesn't bite you later.
Building this in 7 days was a blast. It’s not perfect, but it’s a working tool that solves a real problem I face every single day.
What do you think? Do you have a "todo graveyard" in your current project, or are you actually organized? I'd love to hear how you handle these little tasks!