DebtBomb – Make TODOs expire and automatically create Jira tickets
Hi HN, In most codebases I’ve worked on, temporary hacks (“TODO: remove later”, “just for this release”) slowly become permanent. Nobody remembers why they exist, but they keep shipping to production. I built a small CLI called DebtBomb to make that explicit. Instead of free-form TODOs, you attach an expiry date to temporary code. When the date passes, CI fails until the code is removed or the expiry is intentionally extended. Recently I added integrations so expired debt bombs don’t just fail CI — they become visible and owned: When a debt bomb expires, DebtBomb can automatically create a…
DebtBomb – Make TODOs expire and automatically create Jira tickets launched on January 13, 2026 with 16 votes, #777 of 14,584 launches that month and more than 90% of that year's launches.
In plain words
DebtBomb is a CLI tool that prevents temporary code hacks from becoming permanent by attaching expiry dates to TODOs. When the date passes, CI fails until the code is removed or the expiry is extended. The tool automatically creates Jira tickets with context (file path, owner, reason, code snippet) when debt expires, and can send notifications to Slack, Discord, or Microsoft Teams. It's designed for development teams working on codebases where temporary fixes tend to accumulate and ship to production unintentionally.
written from the facts on this page · September 2026
From the sources
DebtBomb lets teams ship temporary hacks safely by attaching an expiry date to them. When the date passes, the bomb explodes — CI fails, a ticket is created, and your team is notified in Slack, Discord, or Microsoft Teams — forcing the debt to be owned, tracked, and cleaned up instead of silently rotting forever. - jobin-404/debtbomb
DebtBomb is a cross-language technical-debt enforcement tool that scans source code comments for time-limited “debt bombs” and fails CI when they expire. It lets teams ship temporary hacks safely by attaching an expiry date to them. When the date passes, the build fails — forcing the debt to be cleaned up instead of silently rotting forever. TODO: remove later FIXME: temporary workaround They almost never get removed. Temporary code is allowed — but it must be time-bounded, owned, and visiblefrom github.com
In the maker’s words, at launch
Hi HN, In most codebases I’ve worked on, temporary hacks (“TODO: remove later”, “just for this release”) slowly become permanent. Nobody remembers why they exist, but they keep shipping to production. I built a small CLI called DebtBomb to make that explicit. Instead of free-form TODOs, you attach an expiry date to…
Does a similar job
all alternatives →- EIExpiry.io -Reduce your churn rate by avoiding failed payments on Stripe2014 · expiry.io · ▲21
- ZSZyg – Stop Writing Status Updates2025 · zyg.sh · ▲5
Hi HN, I’m Tobi. For a couple of hours over the past few days I’ve been hacking on something to fix a pain point in my dev workflow: writing status updates. Progress is invisible by default. GitHub, Linear, Jira all track tickets and code, but they don’t do a good job of capturing the narrative between “ticket started” and “ticket done.” You start working on a feature, your PM asks “how’s it going?”, and even though you know exactly how it’s going - because you’ve been committing and making progress - you still struggle to answer. That usually means breaking your flow to piece together an…
When Will I Run Out Of Money? (weekend project)2023 · whenwillirunoutofmoney.com · ▲12Hi everyone, I’ve been on Hacker News for a good number of years, but this is my first “Show HN”. I changed jobs recently. Tax is weird in Europe (and maybe other places as well?) in that different amounts go out at different times and repeat at various intervals. I needed to make sure I had enough cashflow to make all upcoming payments, I didn't want any surprises. So I created a little tool for my own purposes, then had fun putting a small HTML frontend on it as I thought it might be useful for someone else. I'm a backend developer in my day job, as you can probably tell from the design :)…
- Dibs — Friendly Debt TrackerJan 2026 · dibs.pablogamero.com · ▲6
Track money between friends and family. Offline, simple.
More dev tools this month
the category →
Contribute to oosexgang/hackios-xnu-kernel development by creating an account on GitHub.
Dev tools · 1d ago · github.com
open-source IDE for thoughtful software design. Contribute to devdotfast/whiteboard development by creating an account on GitHub.
Dev tools · 29d ago · github.com
Contribute to reladraw/reladraw development by creating an account on GitHub.
Dev tools · 27d ago · github.com
OpenBot▲362Grok Bot alternative: free, local, open-source, multiplayer
Dev tools · 24d ago · openbot.run
Talanoa▲346Hi HN, I’m a fullstack developer, and honestly, I’ve lost count of how many side projects I’ve worked on over the years. But one idea kept coming back to me: a different kind of email client. It first came to me in 2014: “What if we could handle emails more like conversations?” Every year, I’d revisit this concept in my “Build Notes.” Ten years later, no one had built exactly what I had in mind — so I finally decided to do it myself. That’s how Talanoa was born. I wanted something focused on people, not timelines. I was tired of marking messages as unread just to remember to reply later, or…
Dev tools · 22d ago · talanoa.email
Source: Show HN post ↗ · launch text quoted in part
Launched alongside, January 2026
the whole month →- IN
Hey HN! I wanted to share something I built over the last few weeks: isometric.nyc is a massive isometric pixel art map of NYC, built with nano banana and coding agents. I didn't write a single line of code. Of course no-code doesn't mean no-engineering. This project took a lot more manual labor than I'd hoped! I wrote a deep dive on the workflow and some thoughts about the future of AI coding and creativity: http://cannoneyed.com/projects/isometric-nyc
AI · Jan 2026 · cannoneyed.com
Automatic AI-powered code reviews the moment you open a PR
Dev tools · Jan 2026 · kilo.ai
