6. Github in Practice
Note: The video covers material not in the guide below — please watch in full.
Action Step
Complete this before moving on.
Open GitHub Desktop, select your personal repo, and commit and push all of your recent changes. Then create a test file in your repo, and this time use Claude Code to commit and push it instead of GitHub Desktop — you may need to figure out the setup for that on your own. Go to your repo on github.com and submit a screenshot of your commits page showing both pushes.
Training Guide
You just built a skill in the last training. Right now it's sitting locally on your machine. It's not backed up. If your laptop dies tomorrow, it's gone.
Time to fix that.
(This is short — because the workflow is simple)
The Exercise
You're going to push your personal repo to GitHub so your work is saved in the cloud.
Step 1: Open GitHub Desktop. Make sure your personal repo is selected in the dropdown in the top left.
Step 2: You'll see your skill file (and any other recent changes) listed in the left panel. Green highlight means new file, yellow means modified.
Step 3: Write a commit message in the Summary field at the bottom left. Something like "Add transcript processing skill" — short, clear, describes what you did.
Step 4: Click "Commit to main." Then click "Push origin" at the top.
That's it. Your work is now backed up on GitHub. You can access it from any machine, and if anything happens to your laptop, nothing is lost.
One More Thing: Claude Can Do This Too
You don't have to open GitHub Desktop every time. Claude Code can commit and push directly from the chat.
Next time you finish a piece of work and want to push it, try:
"Commit my changes with the message 'Add transcript processing skill' and push to GitHub."
Claude runs the git commands in the terminal — same result, no app switching. It's faster when you're in the middle of a workflow and don't want to break your flow.
GitHub Desktop is still great for when you want to visually review what changed before committing — especially at the end of the day when you've touched a lot of files. Both methods do the same thing. Use whichever fits the moment.
A Note on Team Repos
This exact same workflow — commit and push — is how you'd contribute to a shared team repo too. The only difference is which repo you have selected in GitHub Desktop. Instead of your personal repo, you'd switch to the team repo, and your push would be live for everyone. Same steps, bigger audience.
Submission
Screenshot of GitHub Desktop or github.com showing your successful commit and push.
(Next up: you're working with the team playbook library)
Comment in Slack
Post your answer in your onboarding channel.
What was your biggest takeaway(s) from this training?