Make your code
shine brighter.
A refreshing reality check for your GitHub. Discover what recruiters notice, get a playful roast, and turn every rough edge into your next glow-up.
Reading between the commits_
Fetching public profile information...
Your GitHub report card.
An honest snapshot of your portfolio.
—
A transparent portfolio-health score, not a prediction of hiring success.
How fair is this score? What the rules intentionally do not measure
- Scores measure publicly visible portfolio presentation, not hiring potential.
- Stars and followers do not earn points.
30-second recruiter evidence scan Five factual checkpoints, not a hiring prediction
Know what to fix. Then fix it.
One improvement plan, one workshop, no repeated reports.
Less scrolling. More shipping.
Real fixes, ordered by impact. Check them off as you go.
⌕ Browse featured repositories Expand ▾
Featured repositories
Plan the next point.
Select possible fixes to see an illustrative score projection. This is separate from the real audit and your completed checklist.
Run an audit to build your projection.
Planning estimates are never actual audit scores.
Your next seven days.
Prioritized fixes from public evidence, followed by verification and a fresh score check.
Repository Evidence Intelligence
Inspect filenames in the repository selected below in Portfolio Workshop. Look for test, CI, deployment and documentation signals. No files are executed and this does not affect your portfolio score.
Run an audit to enable file-path inspection.
Inspect, then improve.
Check the README and create editable writing suggestions for the same project.
Is your README recruiter-ready?
Choose a repository. See what documentation a visitor can actually find, what's unclear, and what to fix first.
Documentation results
Signals are not proof of working instructions.
Your portfolio, rewritten.
Draft a clearer bio, repository description, and README outline using real public GitHub information.
GitHub bio
Tell visitors who you are and what you work on.
Repo description
Summarize the problem and what the project actually does.
README outline
A starting outline, not a replacement for documenting what you really built.
Suggestions are drafts, not verified facts. Review them before adding them to your profile or repository. GitRoast never edits GitHub on your behalf.
Your progress, in real numbers.
Save today's baseline, improve your public GitHub profile, and recheck to see exactly which signals changed.
Saved only in this browser for each GitHub username—not uploaded to our server. Fresh rechecks bypass the 10-minute cache without calling Gemini, and update this comparison only. Run a new full audit to refresh the main report.
Which areas changed?
Before → AfterWhat the data shows
Observable public signalsScore changes describe public-profile presentation, not programming skill or hiring likelihood.
Three steps to a better profile.
Think of it as a pull request for your personal brand.
Drop your username
We read your public profile and original repositories using GitHub's API. No login, no passwords.
Face the review
See exactly where you shine. Gemini adds witty, constructive feedback whenever available — never hidden behind mystery labels.
Make the next commit
Fix what matters: descriptions, READMEs, live demos, and how you present your best work.
Let your best work
see the light of day.
Your profile doesn't need to be perfect. It needs to tell your story.