Show HN: Codereport – track TODOs, refactors, and bugs in your repo with a CLI

- TODOs are scattered across files/apps/messages

- “Critical” fixes don’t actually block people from collecting debt

- PR comments or tickets aren’t enough actionable

So I built codereport, a CLI that stores structured follow-ups in the repo itself (.codereports/). Each report tracks:

- file + line range (src/foo.rs:42-88)

- tag (todo, refactor, buggy, critical)

- severity (you can configure it to be blocking in CI)

- optional expiration date

- owner (CODEOWNERS → git blame fallback)

You can list, resolve, or delete reports, generate a minimal HTML dashboard with heatmaps and KPIs, and run codereport check in CI to fail merges if anything blocking or expired is still open.

It’s repo-first, and doesn’t rely on any external services.

I’m curious:

Would a tool like this fit in your workflow?

Is storing reports in YAML in the repo reasonable?

Would CI enforcement feel useful or annoying?

CLI: https://crates.io/crates/codereport + codereport.pulko-app.com