Your First GitHub Repo in Claude Code Think of GitHub as a bit like Google Drive for the files that make up an app or an AI skill. One project lives in a repository, or repo. When you save a version and send it to GitHub, you can come back later and see what changed, who saved it, and when. You can download those files on another computer, share them with a teammate, or undo a change that didn’t work. Let’s start with one small project so you can see how that works. If you’re new to GitHub, go to github dot com and choose Sign up. Follow the form to create your free personal account. Then open the email from GitHub and verify your address. Once your account is ready, open Claude Desktop. In Claude Desktop, choose Code and This computer. Open the folder menu, then choose Open folder. I pick an empty folder I made for this example, then click Open. Claude asks whether I trust this folder. I check its name and choose Trust workspace. Paste this prompt and send it. It asks Claude to set up a private repo, prepare the starter files, and show them to you first. If this computer still needs to connect to GitHub, the last line asks Claude to guide you through sign-in. Claude drafts three files. The skill tells it how to turn notes into an update. The readme explains the project to people. Agents dot M D holds a rule for AI tools. I review the files and tell Claude they’re ready. This computer is already signed in through a tool called the GitHub C L I. Claude saves the first version and sends the files to GitHub. Open the link Claude gives you. The files are here. Check the Private label next to the repo name. Click the number of commits to see the history. A commit is a saved version. I’ll switch to the original practice repo for the rest of the video so we can follow one edit through review, testing, and undoing it. Now I want to try a different heading. Main is the primary branch. A branch is a named line of changes. I’m opening another session so I can try the edit on a separate branch. I turn on Worktree. A worktree is another folder on your computer where you can open and edit that branch’s files. I tell Claude I want the heading to say Next steps. I ask to review the edit before I save a version. I open the files side by side so you can see what Claude changed and which folder it changed. The worktree is on the left. That copy has Next steps. The original folder is on the right. Its branch is main, and it still says Action items. Both folders share one repository. The extra folder helps when you want both versions open at once. Claude updated the heading and the example in the readme. I check that those are the two edits I want. Staging means choosing which changes go into the next saved version. I ask Claude to stage these two files and pause. Claude shows me what’s staged. I can review that list before I commit. I ask Claude to commit. A commit saves the changes we chose in the project’s Git history on this computer. Here’s the commit. Its name tells me what it did, and its short ID lets me find this exact version later. The commit is on my computer. I ask Claude to push the branch so I can see that saved version on GitHub. The edit branch now appears on GitHub. Main still has the original skill. I can ask for a review before the edit goes into main. I ask Claude to open a pull request. A pull request is a proposal to add this branch’s changes to main. Claude gives me a link. I open it in GitHub. Choose Files changed. GitHub shows the old heading in red and the new one in green. On a team, this is where someone can review the edit or ask a question. I go back to Conversation and click Merge pull request. Confirming the merge applies the edit to main. The new version is on GitHub. Pulling brings it down to the original folder on my computer. I ask Claude to pull main and try the updated skill on the same note. The note is the same. The heading now says Next steps. That’s the change we wanted to test. What if I decide I preferred Action items? I open the merged pull request and click Revert. GitHub prepares a new pull request that reverses the earlier edit. I open it so I can review that change too. Under Files changed, Next steps is being removed and Action items is going back in. I merge the reversal into main. For a small personal project, you can review, commit, and push your change on main. Teams often use pull requests so someone else can check a change before it goes in. Here’s the commit history. It has the edit and the reversal. That gives me a record of what I tried. Back in Claude, I pull the restored version and try the same note one more time. Action items is back. If you’re getting started, pick a small project like this one. Save one change you can explain, and use GitHub’s history to find it again.