DebtDraft

Spot the risk. Trace the cause. Merge with confidence.

A GitHub Action for your team's CI. Now on the GitHub Marketplace.

[DebtDraft @DebtDraft]

Who's ready for a killer discount on DebtDraft Pro?!

Get 50% off your whole first year with code LAUNCH50 (Annual plan)!

Pro gets you:
Unlimited repos
A health score on every PR
An updating PR comment
Full trend history

Only valid for the first 50 subscribers, so move fast!

[DebtDraft @DebtDraft]

"LGTM!"
...but is it?

Meet DebtDraft.

A GitHub Action that scores every pull request on complexity, coverage, duplication and dependency hygiene.

Spot the risk. Trace the cause. Merge with confidence.

Live now.

[DebtDraft @DebtDraft]

A repo's health isn't one bad day. It's the slope. DebtDraft keeps the history so you can see whether last quarter's habits are helping or hurting.

[DebtDraft @DebtDraft]

Hackathon code often becomes the real product. Run a scan before it does, and you'll know exactly what you're inheriting.

[DebtDraft @DebtDraft]

Code review comments like "this is too complex" are opinions. A measured score on the changed lines is a conversation starter that doesn't feel personal.

[DebtDraft @DebtDraft]

Refactoring is hard to justify to people who don't read code. A score that climbs after the cleanup gives you something to show them.

[DebtDraft @DebtDraft]

Outdated dependencies rarely hurt on the day they age. They hurt on the day you must upgrade in a hurry. Seeing the gap early makes that day boring.

[DebtDraft @DebtDraft]

New teammate, unfamiliar repo. Where do they look first? A score per signal points to the weak spots before they step in them.

[DebtDraft @DebtDraft]

"We'll clean it up later" needs a number to hold it to. A trend line on a dashboard is harder to ignore than a TODO comment.

[DebtDraft @DebtDraft]

Nothing better than seeing your project health increasing over time !!

[DebtDraft @DebtDraft]

AI wrote the function. It passed the tests. Nobody asked how tangled it is. DebtDraft asks, on every pull request, so you don't find out six months later.

[DebtDraft @DebtDraft]

Maintainers review for free, on their own time. A health comment on each PR means the boring checks are done before a human opens the diff.

[DebtDraft @DebtDraft]

Side projects don't die from bad ideas. They die when you return after a month and can't tell what's safe to touch. A health score on every pull request is a note to your future self.

[DebtDraft @DebtDraft]

Building with AI? DebtDraft Pro has something new for you!

Copy for AI turns your latest scan into a prompt in one click. Paste it into your AI assistant or agent and get a phase-by-phase plan to fix what DebtDraft found.

[DebtDraft @DebtDraft]

Who’d like to know what malicious packages they’re using in their repositories?

#codequality #codereview

[DebtDraft @DebtDraft]

Side projects rarely die from one big mistake. They die when the code gets quietly harder to change and the fun runs out. Keeping an eye on the small stuff keeps the project fun.

[DebtDraft @DebtDraft]

Solo devs have no reviewer. That makes the pull request the only place to stop and look at your own work. Even a quick look at what changed beats merging straight from the editor.

[DebtDraft @DebtDraft]

Try DebtDraft for free today! Sign in with GitHub, add one step to your workflow, and your next pull request gets a health score comment.

https://t.co/yk7kUiCuoc

[DebtDraft @DebtDraft]

Technical debt is not bad by itself. Debt you can see is a decision. Debt you cannot see is a surprise.

[DebtDraft @DebtDraft]

Code review is better when the reviewer spends energy on design and not on spotting the stuff a tool can spot. Let the boring checks run themselves.

[DebtDraft @DebtDraft]

Most known vulnerabilities do not live in the packages you chose. They live in the packages your packages chose. Worth knowing before an attacker does.

[DebtDraft @DebtDraft]

Tech debt really creeps up on you if you're not careful