How to make your GitHub profile stand out (README, stats, badges)

Your GitHub profile is the developer homepage you already have. Most people leave it on factory settings; standing out takes about an hour. Here's every lever, in the order visitors see them.

1. The profile README

Create a repository named exactly your username, add a README.md, and its content renders at the top of your profile. That's the whole trick — and most developers still haven't done it.

What works in a profile README:

• One line about what you build — specific beats clever ("I build data-viz tools in Rust" > "code wizard 🧙").
• Current focus — what you're working on now makes the profile feel alive.
• Where else to find you — site, blog, socials.
• A touch of visual life — stats cards or badges (next sections), used sparingly. A README that's all widgets reads like a MySpace page.

2. GitHub stats cards

The popular github-readme-stats project renders live SVG cards — total stars, commits, top languages — you can embed straight in your README:

![Stats](https://github-readme-stats.vercel.app/api?username=YOUR_USERNAME&show_icons=true)
![Top languages](https://github-readme-stats.vercel.app/api/top-langs/?username=YOUR_USERNAME&layout=compact)

Pick one or two. The languages card is the most informative per pixel.

3. Badges

Shields.io generates the small tech badges you see everywhere ("TypeScript", "built with Rust", CI status). Useful in project READMEs to show a stack at a glance; in profile READMEs, a single row is plenty.

4. Achievements

Those hexagonal badges on your profile sidebar — Pull Shark, Quickdraw, YOLO — are awarded automatically by GitHub. You can't add them manually, but you can earn them; we wrote a full breakdown: GitHub achievements, explained.

5. Pinned repositories

Six slots, and they're the only repos most visitors ever see. Choose deliberately: your best work, described in one clear sentence each. An unpinned profile shows your six most recently active repos — which is rarely the story you'd choose to tell. More on this in what recruiters actually look at.

6. The contribution graph

The biggest element on the page, and the one that reads in half a second: active or abandoned? Understand what actually counts as a contribution (default branches, linked emails, timezones), fix the leaks, and keep the graph green with consistent small contributions — or let GitShine maintain a steady, natural-looking baseline on repos you choose, free, while you spend the effort on the layers above.

The one-hour checklist

1. Create the username repo + README (20 min)
2. Add one stats card and a language card (10 min)
3. Pin six repos, write their descriptions (15 min)
4. Set up GitShine or a contribution habit (10 min)
5. Add the profile link to your resume and socials (5 min)

An hour of surface work won't make weak projects strong — but it makes strong work impossible to miss.