FREE AI TOOL
Make your GitHub work like a second resume
Enter your username. The AI reviews your public profile and repos, scores them, and writes a ready-to-paste profile README and better repo descriptions.
Loading…
FREE AI TOOL
Enter your username. The AI reviews your public profile and repos, scores them, and writes a ready-to-paste profile README and better repo descriptions.
Loading…
Profile workbench
Turn your GitHub into the second resume a developer is actually judged on.
“My GitHub is just a list of repo names.”
You get a profile README written for the job you want, plus a description and topics for every repository, ready to paste.
“I have projects but no idea which to show.”
It reads up to 40 of your own public repositories and tells you which six to pin, and why those six.
“I do not know what a recruiter sees when they open my profile.”
A score out of 100 with the breakdown, review notes, top issues and quick wins — the same things a reviewer glances at in ten seconds.
Looks at your public GitHub profile and projects, scores them as a recruiter would, and writes a better profile README, bio, pinned-repository picks and repository descriptions.
Enter your email, press "Send login code", then type the 6-digit code. No password. You can resend the code or use a different email.
Type your username or profile link, for example "octocat" or "github.com/octocat". You do not need to connect your GitHub account or give any token.
For example "backend developer" or "data engineer". The README and pin picks are written for that role.
A progress list shows it fetching your public profile, reviewing repositories, scoring, writing your README and polishing repository descriptions.
Results open like a small file explorer. README.md has Preview, Raw and Diff tabs. bio.txt has bio suggestions. pinned.json shows which repositories to pin. repos/ has a description and topics for each repository. issues.md is your checklist. The side panel shows your profile score out of 100, the score breakdown, review notes, top issues and quick wins.
Use "Copy README" or "Download" for the README, then paste it into a repository named exactly like your username. Use the copy buttons for descriptions and topics, and tick items off in the checklist as you apply them.
Who it is for. Developers and students who want GitHub to work as a second resume.
Free. You get 3 analyses a day per account, resetting at midnight IST. A failed analysis does not use up one of your three.
Worth knowing before you spend anything.
No, and you should be wary of tools that ask. You type your username or profile link and it reads the public API, exactly as any visitor could. There is no token, no OAuth prompt and no write access of any kind.
No. Nothing is pushed, renamed or deleted. You copy the README, the descriptions and the topics and apply them yourself, which means you read everything before it exists on your profile.
In a repository named exactly like your username — that is GitHub's rule for showing a README on your profile page. The tool gives you the file to copy or download, and a Diff tab that shows precisely what changes against your current one.
An account with no public, non-fork repositories cannot be analysed, because there is nothing of yours to review. Make one piece of your own work public first — even a small finished thing beats a forked tutorial.
Yes, if you have one. It is optional, but the README and the pinned-repo picks change noticeably when the tool knows whether you are aiming at backend, data or frontend work.
Fix it before you publish. The AI reads your code's surface — names, languages, README text — not its intent, so it can describe a project imprecisely. Everything it writes is a draft for you to correct, which is why you paste it in yourself.
Free · 3 uses a day