Git Onboarding Workflow
- 8 installs
- 5 repo stars
- Updated February 21, 2026
- ai-native-camp/git-for-everyone
git-onboarding-workflow is a Claude Code skill that analyzes git state and advises the next GitHub Flow step from branch to Pull Request.
About
git-onboarding-workflow analyzes the current git state and tells the user the next step under GitHub Flow. It reads the current branch, working-tree status and unpushed commits, then maps them to one of five situations and suggests the exact command, from creating a feature branch to running gh pr create. A developer runs it when unsure what to do next in the branch-to-PR flow.
- Analyzes current git state and advises the next GitHub Flow step
- Covers five states from clean main to a feature branch ready for a PR
- Suggests the exact branch, commit, push or gh pr create command to run next
Git Onboarding Workflow by the numbers
- 8 all-time installs (skills.sh)
- Ranked #444 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
git-onboarding-workflow capabilities & compatibility
Free; uses git and the GitHub CLI.
- Capabilities
- git workflow · branch management · pr creation · next step advisor
- Works with
- github
- Use cases
- ci cd · devops
- Pricing
- Free
What git-onboarding-workflow says it does
현재 git 상태를 분석하고 GitHub Flow 기준으로 다음 단계를 안내합니다.
브랜치 이름은 `feat/`, `fix/`, `chore/` 등 conventional 접두사를 사용하세요.
npx skills add https://github.com/ai-native-camp/git-for-everyone --skill git-onboarding-workflowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 8 |
|---|---|
| repo stars | ★ 5 |
| Last updated | February 21, 2026 |
| Repository | ai-native-camp/git-for-everyone ↗ |
What it does
Analyze git state and advise the next GitHub Flow step, from feature branch to PR creation.
Who is it for?
Users mid-project who are unsure what git command to run next in GitHub Flow.
Skip if: Initial machine setup, which is handled by git-onboarding-setup instead.
When should I use this skill?
A user asks 'what should I do next', 'workflow', or 'git flow'.
What you get
The skill names the situation and gives the exact next branch, commit, push or PR command.
- next-step recommendation
- exact git or gh command to run
By the numbers
- Handles 5 git-state situations
- Reads 3 git state commands
- Advises branch, commit, push and PR steps
Files
GitHub Flow 워크플로우 가이드
현재 git 상태를 분석하고 다음 단계를 안내합니다.
상태 수집
아래 3개 명령어를 실행하세요:
1. git branch --show-current — 현재 브랜치 2. git status --short — 작업 트리 상태 3. git log @{u}.. --oneline 2>/dev/null — 미push 커밋 (upstream이 없으면 빈 결과)
상태별 안내
결과를 분석하여 아래 5가지 중 해당하는 상황을 안내하세요:
1. main 브랜치, 변경 없음
새 작업을 시작할 준비가 되었습니다.
git checkout -b feat/<기능명>브랜치 이름은 feat/, fix/, chore/ 등 conventional 접두사를 사용하세요.
2. main 브랜치, 변경 있음
main에서 직접 작업한 내용이 있습니다. feature 브랜치로 옮기세요.
git stash
git checkout -b feat/<기능명>
git stash pop3. feature 브랜치, 미커밋 변경 있음
작업 내용을 커밋하세요.
git add <파일들>
git commit -m "feat: 변경 내용 설명"커밋 메시지는 conventional commits 형식을 따르세요.
4. feature 브랜치, 미push 커밋 있음
원격에 push하고 PR을 생성하세요.
git push -u origin HEAD
gh pr create --fill5. feature 브랜치, clean 상태
모든 변경이 push된 상태입니다. PR 상태를 확인하세요.
gh pr statusPR이 없다면 생성하세요: gh pr create --fill
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
How many situations does it handle?
Five, from clean main to a feature branch with all changes pushed and ready for a PR.
What does it do when on clean main?
It tells you to create a feature branch with a conventional prefix like feat/, fix/ or chore/.