SuperAPI AI Directory

git-onboarding-step

Coding & development

View repository

Updated 10-15 18:25

About this skill

Git Progress Checklist

Check the progress of all 10 steps and guides you through the current step. This skill only shows the status, and delegates actual execution to /git-onboarding-setup or /git-onboarding-workflow.

Status Collection

Run the commands below all in parallel :

  1. which git — Whether Git is installed
  2. git config --global user.name — User name
  3. git config --global user.email — Email
  4. which gh 2>/dev/null && echo "installed" || echo "none" — Whether GitHub CLI is installed
  5. gh auth status 2>&1 — GitHub authentication status
  6. git rev-parse --git-dir 2>/dev/null && echo "repo" || echo "no-repo" — Whether a repository exists
  7. git branch --show-current 2>/dev/null — Current branch
  8. git log --oneline -1 2>/dev/null — Whether commits exist
  9. git log @{u}.. --oneline 2>/dev/null — Unpushed commits
  10. which gh >/dev/null 2>&1 && gh pr list --head "$(git branch --show-current 2>/dev/null)" --json number --jq '.[0].number' 2>/dev/null || echo "gh-unavailable" — Whether a PR exists

Checklist Evaluation

Completion conditions for each item:

Step Item Completion Condition
1 Install Git which gitReturns this path
2 Set user name git config --global user.nameThis is not empty
3 Set email git config --global user.emailThis is not empty
4 Install GitHub CLI which ghReturns a path
5 GitHub login gh auth status Output includes "Logged in"
6 Prepare repository git rev-parse --git-dir Success
7 Create branch Current branch is a feature branch, not main/master
8 First commit git log --oneline -1Returns a result
9 Push git log @{u}..Returns an empty result (no unpushed commits)
10 Create Pull Request The PR number for the current branch is confirmed with the gh CLI

Special Evaluation Rules

  • Step 7: Incomplete if on main/master. However, if the repository does not exist (Step 6 incomplete), evaluation is not possible → treat as incomplete
  • Step 9: Incomplete if the command fails because upstream is not set
  • Step 10: If the gh CLI is not installed (gh-unavailable), display as "Cannot verify"

Output Format

Output in the format below inside a code block.

  • Completed items: [x]
  • Incomplete items: [ ]
  • Next to the first incomplete item: <-- 현재 단계
  • For steps 2 and 3, when complete, show the configured value in parentheses
  • If step 10 cannot be verified: [?]Display as
Git 시작하기 — 현재 진행 상황

  [x] 1. Git 설치
  [x] 2. 사용자 이름 설정 (홍길동)
  [x] 3. 이메일 설정 (user@email.com)
  [x] 4. GitHub CLI 설치
  [ ] 5. GitHub 로그인            <-- 현재 단계
  [ ] 6. 저장소 준비
  [ ] 7. 브랜치 생성
  [ ] 8. 첫 번째 커밋
  [ ] 9. Push
  [ ] 10. Pull Request 생성

Current Step Description

After outputting the checklist, guide the user through the following for the first incomplete step:

Step 1: Install Git

  • Why it is needed: Git is a tool for managing the history of code changes. It is the foundation of all work.
  • How to resolve: /git-onboarding-setup Run .

Step 2: Set user name

  • Why it is needed: When you commit, it records "who made this change." It is essential for collaboration.
  • Solution: /git-onboarding-setup Run .

Step 3: Email Settings

  • Why it's needed: It is used by GitHub to link commits with your account. It must match your GitHub account email for contributions to be planted.
  • Solution: /git-onboarding-setup Run .

Step 4: Install GitHub CLI

  • Why it's needed: GitHub CLI (gh) is a tool that makes it easy to log in to GitHub, create PRs, etc. from the terminal.
  • Solution: /git-onboarding-setup Run .

Step 5: Log in to GitHub

  • Why it's needed: You must log in to GitHub to push/pull and create PRs.
  • Solution: /git-onboarding-setup Run .

Step 6: Prepare the Repository

  • Why it's needed: You need a project folder to manage with Git. Start with clone (existing project) or init (new project).
  • Solution: /git-onboarding-setup Run .

Step 7: Create a Branch

  • Why it's needed: The main branch keeps only completed code. New features should be worked on in a separate branch to be safe.
  • Solution: /git-onboarding-workflow Run .

Step 8: First Commit

  • Why it's needed: A commit is a "save point" for your work. You can return to this point at any time.
  • Solution: /git-onboarding-workflow Run .

Step 9: Push

  • Why it's needed: You need to upload local commits to GitHub so others can see them and so they are backed up.
  • Solution: /git-onboarding-workflow Run .

Step 10: Create a Pull Request

  • Why it's needed: A PR is a request saying "please merge this change into main." You can receive code reviews.
  • Solution: /git-onboarding-workflow Run .

When everything is complete

Once all 10 items are complete:

Git 시작하기 — 전체 완료!

  [x] 1. Git 설치
  [x] 2. 사용자 이름 설정 (...)
  [x] 3. 이메일 설정 (...)
  [x] 4. GitHub CLI 설치
  [x] 5. GitHub 로그인
  [x] 6. 저장소 준비
  [x] 7. 브랜치 생성
  [x] 8. 첫 번째 커밋
  [x] 9. Push
  [x] 10. Pull Request 생성

축하합니다! Git 설정부터 PR 생성까지 모든 과정을 완료했습니다.
이제 GitHub Flow에 따라 자유롭게 개발하세요.