I got tired of spending days untangling inherited codebases, so I built a tool that does it in minutes
Hello Indie Hackers!
I've been a developer for a long time — I'm 58, I'm neurodivergent, and I've learned that the problems worth solving are the ones that annoy you repeatedly.
For me, that problem is inheriting messy GitHub repos.
You know the drill: no documentation, inconsistent patterns, five different ways to do the same thing, and a sinking feeling that it'll take a week just to figure out where to start.
I kept doing this painful unscrambling over and over. So I built something to automate it.
CodeDecipher.app takes a GitHub URL, analyzes the codebase with AI, and gives you:
What the code actually does
How it's organized (or isn't)
Where to start if you need to modify or refactor it
You can run a security scan, an API documentation analyzer, or enter code in chunks.
What I've learned since launching:
I started with a subscription model. Then I watched how people actually used the tool — and realized most people needed it once, when they inherited a messy repo. Paying monthly for a rescue didn't make sense.
So I'm pivoting to a hybrid model:
Pay-per-use for one-off rescues
Subscription for teams or anyone who needs ongoing access
V2 is in the works with a chat feature that allows you to dig even deeper into your code and features that actually reward returning users. The current version is live, free to try, and there's a demo video on the landing page if you want to see it in action.
I'd love feedback from other devs who deal with inherited code:
What do you wish you knew about a codebase before diving in?
How do you currently untangle a repo you didn't write?
Anyone else wrestled with pricing a tool that people use episodically?
The episodic pricing problem is one of the hardest things to get right. Subscription makes sense when the pain is ongoing but you're right that inheriting a codebase is usually a one time rescue job. The hybrid model sounds like the right call - let the use case dictate the pricing rather than forcing a model that doesn't fit the behavior.
The question I'd ask is whether there's a way to create ongoing value for the same user. If someone inherits a messy repo today, in 6 months they might be the one handing off a messy repo to someone else. That's a different problem but same person. Might be worth thinking about what brings them back before V2. Good luck with the pivot.
That's something I hadn't considered--someone inheriting mess and then passing on mess. Thats wild! I like the hybrid pricing model for this as people already using it can stay on the same plan or change it up. My other pain point is logistics--where do I find my people? That seems to be the million dollar question!