gh-setup

Installation
SKILL.md

Repo Setup (solo dev)

A well-set-up repo, solo, is the minimum that protects you and your users — and nothing beyond it. Most GitHub setup advice is written for teams and orgs: CODEOWNERS, required reviewers, elaborate templates, protection rules with human approval gates. Almost all of that is friction for one person. What's left, once you strip the team ceremony, is a short list that genuinely pays: a repo someone can understand, secrets kept out of history, and a CI robot standing in for the reviewer you don't have.

Scaffolding a new repo

The files that make a repo legible and safe from commit one:

  • README — what it is and why, how to install, how to run it. Written for a stranger (often future-you). Keep it to what a newcomer needs; run it through the keep-it-human skill so it reads like you, not a generated template.
  • LICENSE — pick one deliberately; "no license" means nobody may legally use it. GitHub's picker or gh repo create will add it.
  • .gitignore — start from the language-appropriate template (GitHub offers one per language at repo creation, or use the community templates) so build output, deps, and local files never get committed. Add your own env/secret paths on top.
  • Default branch main, and turn on the housekeeping toggles below.

gh repo create <name> --private --license mit --gitignore Node --clone scaffolds most of this in one shot; exact flags and follow-up commands are in references/gh-commands.md.

Keep secrets out of git — and know what to do when one slips in

Never commit secrets. .gitignore your .env and anything holding a key, and commit a .env.example with the names and dummy values so the shape is documented without the secrets. Turn on GitHub's secret scanning and push protection (free on public repos, and on private with Advanced Security) — push protection catches a key before it leaves your machine, which is the only truly clean save.

Installs
1
Repository
lelborn/skills
First Seen
Jul 23, 2026