| name | navigating-github |
| description | First-time GitHub setup and interactive git learning. Walks users from
zero to a working GitHub repo, then teaches git through 9 hands-on
lessons on their actual project. Adapts language and depth to skill
level — inferred from environment, not questionnaires. Two modes:
Setup (guided onboarding) and Learn (progressive curriculum from
commits to CI/CD). Use when the user asks to set up GitHub, learn
git, or says "teach me github". Trigger with "set up my repo",
"help me with github", "teach me github", "learn git", "what are
branches", "teach me PRs", or "how do I use github".
|
| allowed-tools | Read, Write, Glob, Grep, Bash(git:*), Bash(gh:*), Bash(ssh:*), Bash(test:*), Bash(echo:*), AskUserQuestion |
| version | 2.0.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | MIT |
| compatible-with | claude-code, cursor, windsurf, aider, continue |
| tags | ["github","git","beginner","intermediate","advanced","vibe-coding","version-control","learning","onboarding"] |
Navigating GitHub
First-time GitHub setup and interactive git learning. Get set up, then learn by doing.
Table of Contents
- Overview — 2. Prerequisites — 3. Instructions — 4. Modes — 5. Examples — 6. Output — 7. Resources
Overview
Problem: Getting started with GitHub is the #1 barrier for people building with AI. Beginners stall at setup, don't understand commits vs pushes vs PRs, and have nobody to walk them through it hands-on. AI coding tools can run git commands, but they don't teach you what those commands mean or guide you through setup from scratch.
Solution: Walk users through GitHub setup step by step, then teach git and GitHub through 9 progressive hands-on lessons on their actual project. Every lesson uses do-then-explain: run the command, see the result, then understand why. Adapts language and depth to skill level automatically.
Prerequisites
- Terminal access with
git installed
gh CLI installed (Setup handles installation if missing)- GitHub account (Setup handles creation if missing)
Instructions
Step 1 — Route
Determine mode from the user's request. Act immediately — no preamble.
- No
.git/ directory OR gh auth status fails → Setup (check with test -d .git and gh auth status)
- Keywords "teach", "learn", "what are", "how do", "explain", "lesson" → Learn
- Keywords "set up", "new repo", "init", "get started" → Setup
- Generic ("help me with github") → check environment, route to Setup if no repo, otherwise offer lesson menu
Step 2 — Infer Skill Level
Each mode runs git status as part of its normal operation. Infer level from those signals — no extra commands:
- Only
main branch + short/vague commit messages → Beginner
- A few branches + descriptive commits → Intermediate
- Branch naming conventions + conventional commits → Advanced
- Complex history, multiple remotes, CI configured → Expert
Only ask via AskUserQuestion when signals are genuinely ambiguous. Read ${CLAUDE_SKILL_DIR}/references/skill-assessment-guide.md for the full adaptive behavior matrix. Apply:
