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…
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
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 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 Jira ticket with file path, owner, reason, and code snippet. It can also notify Slack, Discord, or Microsoft Teams. You can configure “expiring soon” warnings (e.g., 7 days before) so it’s not just a surprise break. Repo: https://github.com/jobin-404/debtbomb This is still early and I’m mainly trying to validate whether this actually improves how teams handle “temporary” code compared to TODOs, linters, or just creating tickets manually. I’d especially love feedback from people who’ve dealt with tech debt in long-lived codebases or CI-heavy environments. Thanks for reading.
Does the same job
all alternatives →- ETEnforcing time-bounded technical debt with Git historyJan 2026 · github.com · ▲6
I kept running into the same problem in large codebases: “temporary” code almost never gets removed. People add TODOs, FIXMEs, or quick hacks to hit a deadline, and six months later nobody remembers why they’re there or who owns them. They quietly turn into production bugs. I built a small CLI that treats those comments as time-bounded instead of permanent. You can attach an expiry date to a TODO in the code, and when the date passes, CI fails and points to exactly where the expired code lives. It works by: scanning comments across any language parsing structured annotations and optionally…
- 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…
More dev tools this month
the category →
The first open-source price index for GPU compute Discussion | Link
Dev tools · 10d ago · producthunt.com
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 2d ago · opentrailpaper.com
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
