Growing technical debt, flagged from code patterns before the refactor becomes a rewrite.
Tech debt never announces itself. It accrues in shortcuts labeled 'temporary,' in files nobody wants to open, and in the slow rise of 'how is this so hard to change?'
By the time debt is undeniable, it is also expensive. The cheap moment to name it was six months ago, when it was still small enough to schedule.
This routine watches code patterns across your repos and flags where debt is accumulating: growing complexity, repeated workarounds, the files everyone fears.
You get the early ledger, when paying down debt is still a sprint item instead of a quarter-long excavation.
Copy this prompt into a new Littlebird routine. Edit the days and times to fit your schedule.
Every Friday flag areas of technical debt I noticed this week in code reviews or discussions
Skills are a good demo. You open a chat, paste in yesterday's context, and get a pretty solid answer -- once.
Tomorrow you do the whole thing again: same paste, same wait. The skill does not know your meetings, your threads, or what changed since Monday.
This routine knows all of that before it runs. It fires on schedule and hands you the result where you already work.
From patterns in the code and its history: churn hotspots, complexity growth, and the workaround trails teams leave behind.
It reports to you. What becomes a ticket, and when, stays an engineering decision.
Sure. Point the prompt at a single repo or keep it across all of them.
After the 14-day free trial, Plus costs $17 monthly ($20 month-to-month) and routines are part of the package.
Plus is priced at $17 a month ($20 month-to-month); students get a $15 plan and teams pay $17 per seat.
Fourteen days cost nothing; after that it is $17 a month on Plus, or $20 if you go month-to-month.
Put Littlebird to work.
