I Built a Tool That Turns TODO Comments Into Actual Documentation

Most developers already “document” their code — just not in a structured way. We write things like: // TODO: optimize this // BUG: fix crash here // NOTE: handle edge case Over time, these comments pile up across files, and eventually… they become invisible. I ran into this problem while working on multiple small projects. I knew I had pending work scattered across the codebase, but there was no simple way to track it without introducing another tool or workflow. So I built DocTrack. 💡 The Idea Instead of forcing developers to adopt a new system, I wanted to reuse what already exists inside the code. DocTrack scans a project and extracts structured information from inline comments: What needs to be done (TODO, BUG, etc.) Where it exists (file + line) What context it belongs to (code block) The goal is simple: Turn implicit developer notes into explicit, usable documentation. ⚙️ How It Works At a high level, the tool: Recursively scans a directory using C++17 filesystem APIs Reads file