A repository's first hour decides its fate. Visitors judge the name, the description, the README and the topics before they read a single line of code. This tool audits a GitHub repository before launch and scores ten readiness signals 0-10, so you see what your first users will see - while you can still fix it.

$ github-launch-checklist repoboost-hq/buy-github-stars

GitHub Launch Readiness
────────────────────────

Repository name      ✓ descriptive and searchable
Description          ✓ present and well sized
Topics               ✓ 8 topics
README               ✓ 743 words
License              ✓ MIT
Demo                 ✓ homepage set
Installation         ✓ installation or quick start found
Contributing guide   ✓ guide present
Issue templates      ✓ templates present
Social preview       ⚠ check manually in repo Settings

Launch readiness: 9.5/10

Every check is explained in docs/checks.md - including why it matters and how to fix a fail.

pip install git+https://github.com/repoboost-hq/github-launch-checklist.git

github-launch-checklist owner/repo

Or run it without installing:

python checklist.py owner/repo

github-launch-checklist owner/repo            # readiness report
github-launch-checklist owner/repo --json     # machine-readable output
github-launch-checklist owner/repo --strict   # exit 1 if readiness < 8/10
--token $GITHUB_TOKEN                          # optional, raises API rate limit

Works on any public repository. No token required for occasional use.

Available on the GitHub Marketplace - add it to any workflow in one step.

- uses: repoboost-hq/github-launch-checklist@v1
  with:
    repo: owner/repo     # optional - defaults to the calling repository
    fail-under: 8        # optional - fails the step below this score

docker run --rm ghcr.io/repoboost-hq/github-launch-checklist owner/repo

GitHub search weighs a repository's name, description, topics, README and engagement together. Most repositories fail their first impression not because of the code, but because the name is vague, the About line is empty, the topics are missing or the README never explains how to install anything.

This checklist is the pre-flight version of that reality: fix the ten things above and the repository is discoverable, credible and easy to adopt from day one.

• Why is my repo not showing in GitHub search? - the short answer: an empty description or missing topics.
• Ranking your repository for keywords after launch is a different job - that is what a GitHub search ranking service is for.

Is it free? Yes - MIT licensed, open source, no sign-up, no limits beyond GitHub's API rate limits.

Do I need a token? No. A token only raises the rate limit if you audit many repositories in a row.

Why does it want at least 5 topics? Topics are how GitHub search filters discover repositories. Under 5 topics, you are invisible in most filtered searches. 5-10 relevant topics is the sweet spot.

Is the social preview automated? No - GitHub's API does not expose it, so the tool flags it as a manual check. Set it in repository Settings.

Can I use it in CI? Yes: --strict exits non-zero below 8/10, so a workflow step fails when a repository regresses.

It says I am not ready - what do I fix first? The fails in order: description, installation section, topics, license. Those four move the needle most.

• github-ranking-audit - scores a repo's GitHub search ranking signals
• github-stars-history - track star velocity over time

More from the org: github.com/repoboost-hq

🌐 buygithub.com  |  🧰 More from the org

_{Built by RepoBoost. Independent service, not affiliated with GitHub, Inc.}