Git Insight

Situation

A GitHub profile is a wall of repository names. Recruiters judge developers from it every day with no real way to read it, so good candidates get missed and bad ones get through.

Task

• Turn a username into a structured read: archetype, stack, strengths, role fit.
• Accept whatever gets pasted — a username or a full profile URL.

Result

A profile becomes a seven-card assessment written for the person doing the hiring, not the person being hired.

My Contribution

• Wrote for the reader rather than the developer: a recruiter needs a verdict they can act on, so the model fills a fixed structure instead of producing prose someone has to interpret.
• Caught before launch that the original design would have shipped my API key to every visitor — Vite inlines prefixed variables straight into the bundle. Both keys moved server-side.
• Cut to the top 30 repositories: sending a whole profile costs more and says less.