octocatprofile
Public data only

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…

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.

0 steps, start to finish0 things you take away~1 minute your first run

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.

  1. Log in

    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.

  2. Enter your GitHub

    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.

  3. Add a target role (optional)

    For example "backend developer" or "data engineer". The README and pin picks are written for that role.

  4. Press "Analyse my GitHub"

    A progress list shows it fetching your public profile, reviewing repositories, scoring, writing your README and polishing repository descriptions.

  5. Explore your results

    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.

  6. Copy it into GitHub yourself

    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.

  • A profile score out of 100
  • A ready-to-paste profile README
  • Bio suggestions
  • Which repositories to pin
  • Better descriptions and topics for each repository

Have this ready

  • Your GitHub username or profile link
  • At least one public repository that is not a fork
  • Optional: the kind of job you want

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.

  • Free — 3 analyses a day, resetting at midnight IST
  • No GitHub connection, no token, no permissions. Just your username
  • Public data only: your profile, your own repositories, your profile README
  • A failed analysis does not use one of your three

  • Set a target role: the README changes noticeably.
  • Make your best work public and original; only your own (non-fork) repositories, up to 40, are considered.
  • Use the Diff tab to see exactly what changes against your current README.
  • Read everything before publishing; the AI can be wrong about details.

Where it stops

Worth knowing before you spend anything.

  • It reads public information only and never touches private repositories.
  • It does not change anything on GitHub. You paste the results in yourself.
  • An account with no public non-fork repositories cannot be analysed.

  • Do I have to connect my GitHub account?

    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.

  • Does it change anything on GitHub?

    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.

  • Where does the profile README go?

    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.

  • What if all my repos are forks?

    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.

  • Should I set a target role?

    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.

  • It got a detail about my project wrong. Now what?

    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.