Show HN: BuildFix– Semantic feature-extraction transfer between TypeScript repos
1 points
12 hours ago
| 1 comment
| buildfix.dev
| HN
Hey HN,

I'm Rich. I run a SOC by day and built this at night over the past 6 weeks.

*What it does:* BuildFix treats features (as opposed to files) as complete, transferable units. Select "Auth System" and it identifies routes, middleware, models, config, and secrets handling. Then it traces all dependencies, adapts the files to your target project's conventions, and creates a PR that actually builds.

*The tech:* - TypeScript AST analysis for semantic understanding - PageRank-based import traversal for context selection - Dual knowledge base system (source + target) for convention adaptation - 5-layer validation: AST → TypeScript → ESLint → imports → backward compatibility

*What makes it different from Copilot/Cursor:* Those tools generate code. They don't understand features as first-class entities, can't trace feature completeness across a codebase, and can't guarantee operational parity in another repo.

*The "oh shit" moment:* It used itself to improve itself. BuildFix scanned its own codebase, generated docs about its patterns, then used those docs to refactor 100+ lines when I added 3 lines of new code. Unprompted.

*Stack:* Next.js 14, TypeScript, Redis, Clerk, Vercel *Pricing:* Bring Your Own Key, Free for as long as I can keep it free.

Happy to answer questions about the architecture or approach.

RichBennett
11 hours ago
[-]
Here's a demo video of me transferring a feature from one GitHub Repo to another: https://youtu.be/XygofNNLtHY

Watch it adapt the file on its way from source repo to its destination in order to match the target website's formatting!

reply