devbio
FeaturesExamplesMarketplaceToolsBlogsPricingFAQ
Sign inClaim your slug
All free tools

GitHub profile README

Fill the form, copy the markdown, paste into your <username>/<username> repo. No AI prompts, no shields.io URL templates — just clean output that mirrors a devbio so you only ever maintain one surface.

Identity

About

Stack

Now (optional)

Projects

GitHub widgets

README.md
<h1 align="center">Hi, I'm Sam Linwood 👋</h1>
<p align="center"><em>Indie hacker building developer tools, one Friday at a time\.</em></p>

<p align="center">🌐 <a href="https://samlinwood.dev">website</a>&nbsp;&nbsp;·&nbsp;&nbsp;𝕏 <a href="https://x.com/samlinwood">@samlinwood</a>&nbsp;&nbsp;·&nbsp;&nbsp;🪪 <a href="https://devbio.me/samlinwood">devbio</a></p>

<p align="center"><sub>📍 Lisbon, PT</sub></p>

## About

Ex-platform engineer turned solo founder. I build small, focused tools for developers.

## Stack

![typescript](https://devbio.me/api/tools/badges/typescript.svg) ![react](https://devbio.me/api/tools/badges/react.svg) ![nextjs](https://devbio.me/api/tools/badges/nextjs.svg) ![nodedotjs](https://devbio.me/api/tools/badges/nodedotjs.svg) ![postgresql](https://devbio.me/api/tools/badges/postgresql.svg)

## Now

- Building Logbook full-time
- Open-sourcing the OAuth rotation pieces
- Reading: A Philosophy of Software Design

## Projects

- **[Logbook](https://logbook.app)** — A privacy\-first journaling app for engineers _($4\.2K MRR)_
- **[Tokenfox](https://github.com/samlinwood/tokenfox)** — Drop\-in OAuth token rotation service _(912 ⭐)_

## Stats

<p align="center"><img height="160" src="https://github-readme-stats.vercel.app/api?username=samlinwood&show_icons=true&theme=transparent&hide_border=true" alt="" />
  <img height="160" src="https://github-readme-streak-stats.herokuapp.com/?user=samlinwood&theme=transparent&hide_border=true" alt="" />
  <img height="160" src="https://github-readme-stats.vercel.app/api/top-langs/?username=samlinwood&layout=compact&theme=transparent&hide_border=true" alt="" /></p>

---

<p align="center"><sub>Generated from <a href="https://devbio.me/samlinwood">devbio.me/samlinwood</a> · README stays in sync when the bio changes.</sub></p>

On this page

  • What is a profile README
  • Setting up the special repo
  • Anatomy of a good README
  • The widgets we use
  • FAQ
Guide

GitHub profile READMEs, without the AI fluff

GitHub profile READMEs are one of the few surfaces a developer touches that's both indexed and read by humans. A good one says who you are, what you're working on, and how to find you in 30 seconds. A bad one is 14 emojis, a typing GIF, and a wall of shields.io badges. This guide is the short, opinionated version.

What is a profile README

GitHub gives every user a "hidden" repo whose name matches their handle — github.com/yourname/yourname. If that repo has a README, GitHub renders it at the top of your profile page. Add a file → instant homepage.

Setting up the special repo

One source of truth

Skip the form next time.

On a devbio, every field above is already filled in — your bio components regenerate the README on every change. Edit once, push twice.

devbio.me/
devbio

The developer-first bio platform.

© 2026 devbio.me

Product
ComponentsExamplesMarketplaceResume builderPricingBlogs
Free tools
All toolsOpen Graph previewerMRR calculatorUsername availabilityTech-stack badges
Company
Twitter

One-time, two minutes:

  1. Create a new public repo with the exact name as your GitHub username.
  2. Add a README.md to the root. GitHub will pop a hint banner about this.
  3. Paste the markdown from this tool. Commit.
  4. Visit github.com/yourname to see it.

Any time you want to update, edit the same README.md — pushes show up instantly on your profile.

Anatomy of a good README

The structure that has stood up over the last few years:

  • Headline — your name, one tagline. Centred. No emoji farm.
  • Identity row — three or four links: website, X, email, devbio. Recruiters use this.
  • About — two sentences max. What you build, who for, why.
  • Stack — five badges. Lead with language, follow with framework, finish with cloud / infra. Five honest beats ten aspirational.
  • Now — three bullets of what's on your plate right now. This is the section that signals you're active.
  • Projects — 3-6 rows, each with a name, a one-line description, and a metric (MRR / stars / users).
  • Stats widgets — optional. Adds visual texture without writing more prose.

The widgets we use

We embed three community-maintained widgets — none of them ours:

  • github-readme-stats (vercel.app/api?username=…) — total stars, commits, PRs.
  • github-readme-streak-stats — current + longest streaks.
  • top-languages (same project as the first) — language breakdown by repo.

They render as SVGs that GitHub re-fetches every few hours. We bake the URL into your README so it always pulls fresh.

FAQ

Why no AI?
Generating bio prose with an LLM produces work that reads like every other LLM bio — same cadence, same metaphors, same emoji placement. The bio is the shortest thing you'll ever write in your career; you can write it yourself.
Does this work if my GitHub repo doesn't share my devbio?
Yes — every field is editable. The devbio integration is a shortcut, not a dependency. Skip it and you have a generic README generator that beats every shields.io-based competitor on output quality.
How do I update the README when my bio changes?
Right now: regenerate, copy, push. On the roadmap: a one-click sync from a devbio that opens a pull request against your profile repo via the GitHub App. Drop a note on the repo if you want that prioritised.
Will the widgets stay alive?
github-readme-stats has 60k+ stars and has been maintained since 2020 — about as safe a third-party dependency as you can pick. If it ever shuts down, we'll mirror the widgets ourselves.
Can I include the MRR chart from my devbio?
That's landing in the next release — we'll expose a static SVG of your MRR widget at /api/og/mrr/<slug> so it embeds cleanly in any README.
GitHub
Privacy
Terms