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

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

I got tired of TODOs, temporary hacks, and refactors that never get addressed. In most repos I work on:- TODOs are scattered across files/apps/messages - “Critical” fixes don’t actually block people from collecting debt - PR comments or tickets aren’t enough actionableSo 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 Comments URL: https://news.ycombinator.com/item?id=47067795 Points: 2 # Comments: 0

---

**[devsupporter 해설]**

이 기사는 Show HN에서 제공하는 최신 개발 동향입니다. 관련 도구나 기술에 대해 더 알아보시려면 원본 링크를 참고하세요.