What GitHub is,
and how an operator actually uses it.

A shared, versioned filing cabinet.

GitHub is a place on the internet where a project's files live, with a full history of every change ever made to them. Git is the tool that tracks the changes. GitHub is the website that hosts them and lets people work on the same files without overwriting each other.

For an operator the value is not the code. It is the history and the safety. Every change has a name, a date and a reason. Anything can be undone. Two people, or a person and an AI, can work at the same time without stepping on each other.

Six words that cover most conversations.

1. Repo.

   The project folder, with its history. One business system, one repo.

2. Commit.

   A saved snapshot with a message saying what changed and why. 'Fix the interview scorecard math' is a commit.

3. Branch.

   A copy of the project where work happens without touching the live version. When it is ready, it gets merged back.

4. Pull request.

   The request to merge a branch, with the changes laid out for someone to review before they go live.

5. Main.

   The branch that is the real, live version. Protect it. Nothing lands there without review.

6. Clone.

   Downloading the repo to a computer so you or an AI tool can work on it.

The AI works in a branch, you approve the merge.

AI coding tools are fast and confident, and sometimes wrong. GitHub is how you let them work without letting them break anything. The AI works in a branch. It commits with a message. You read the pull request. You merge, or you do not. Nothing reaches main without a human deciding it should.

• Never let an AI tool push straight to main.
• Read the commit message before you read the code. If the message is vague, the change probably is too.
• One task per branch. A branch called 'fixes' is a branch you cannot review.

Create an account, make one repo, make one commit.

Create a free account. Make a private repo with a plain name. Add one file, even a text file with your brain file in it. Commit it with a message. That is the whole first hour, and after it the words in this guide stop being abstract.

Plan the one repo you will make today.

Name it, decide what goes in it, and write the first commit message. Entries stay on this page and are not sent anywhere.

Have the AI walk you through it.

Use this with an AI coding tool that can see your computer. It sets up the repo and explains each step as it goes.

I run a business and I am not an engineer. Help me set up my first GitHub repo and make my first commit, explaining each step in one plain sentence before you do it.
1. Check whether Git and the GitHub tool are installed. If not, tell me the exact command to install them and wait.
2. Create a private repo named [name] with a README that says what the project is for.
3. Add my brain file to it.
4. Make the first commit with a clear message and show me what the commit looks like.
5. Create a branch for the next piece of work and explain, in two sentences, why you did not work on main.
Do not run any command that deletes or overwrites files without asking me first.

One prompt. Paste it into Claude. It builds the whole thing for your business.

The Pro pack is a build prompt with blanks for your context: your product, your medium, your team. Fill them in, answer its questions, and it produces the complete system in your words. The PDF explains the method so you can judge the output. The setup walkthrough, the daily cheat sheet, commit and PR conventions, the folder structure for running a business (not just code) on GitHub, recovery recipes, and three prompts.