Install the "git-teacher-status" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-status into .claude/skills/git-teacher-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-status", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-status -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "git-teacher-status" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-status into .agents/skills/git-teacher-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-status", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-status -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "git-teacher-status" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-status into .cursor/skills/git-teacher-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-status", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-status -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "git-teacher-status" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-status into .gemini/skills/git-teacher-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-status", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-status -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "git-teacher-status" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-status into .github/skills/git-teacher-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-status", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-status -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "git-teacher-status" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-status into .opencode/skills/git-teacher-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-status", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
git-teacher-status
GitHub stars
128
Token cost
~1k tokens
SKILL.md length
405 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT
At a glance
Translates current Git status into plain-language explanations for non-developers.
Works in 4 steps: 병렬 상태 수집 → 안전 검사 → 상태 번역 → …
Tasks that involve Git workflow
SKILL.md covers 실행 순서, Step 5: Branch 상태 안내, Step 6: Stash 상태 확인 and 복합 상태 처리, plus 2 more sections
Calls git
What it does
Git Teacher Status is an agent skill from fivetaku/gptaku-plugins-codex. Translates current Git status into plain-language explanations for non-developers. Korean triggers — "상태 확인", "지금 어떤 상태?", "뭐가 바뀌었어?", "git status", "변경 사항", "뭐가 달라졌어?", "파일 확인". English triggers — "check status", "what changed", "git status".
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Git workflow and Plain language and style rules. It works with Git and GitHub. The repository describes itself as: Codex-native GPTaku plugin marketplace. The licence is MIT.
When your agent uses it
Tasks that involve Git workflow
Tasks that involve Plain language and style rules
Example prompts
“git status”
“. English triggers —”
“what changed”
“/git-teacher-status”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d3b47fc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Git Teacher Status loads about 1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 405 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~66
When it runs· the whole SKILL.md, loaded when a task matches
~1k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/git-teacher-status/SKILL.md (or your agent's skills folder).
name
git-teacher-status
description
Translates current Git status into plain-language explanations for non-developers. Korean triggers — "상태 확인", "지금 어떤 상태?", "뭐가 바뀌었어?", "git status", "변경 사항", "뭐가 달라졌어?", "파일 확인". English triggers — "check status", "what changed", "git status".
상태 확인 (바르다 깃선생 — Codex)
git status와 관련 명령의 결과를 비개발자가 이해할 수 있는 한국어 자연어로 번역한다.
설명·교육 시 git-teacher-help의 §교육 원칙(shared/questioning-policy.md §3 Teaching)을 따른다. 상태가 헷갈리는 초보에게는 비유로 안심시키며 천천히 짚어준다(§2a). 사용자가 그냥 결과만 빨리 원하면 핵심만 번역해서 준다(§2c).
Codex CLI에는 객관식 카드 UI가 없다. 결정이 필요한 곳은 shared/questioning-policy.md §A의 채팅 번호형 선택지 블록으로 묻는다.
실행 순서
Step 1: 병렬 상태 수집
다음 명령을 병렬로(가능한 한 함께) 실행한다:
bash
git rev-parse --is-inside-work-tree # .git 존재 확인
git symbolic-ref --short HEAD # 현재 branch (detached HEAD 감지)
git status --porcelain # 변경 파일 목록
git log --oneline -3 # 최근 저장 기록 3개
git remote -v # 원격 연결 상태
git stash list # 임시 저장(stash) 확인
Step 2: 안전 검사
우선순위 순서로 검사하고, 문제 발견 시 즉시 안내 후 중단:
.git 없음: "여기는 Git 프로젝트 폴더가 아니에요. '깃 시작해줘'로 먼저 설정하세요." → 중단
Detached HEAD: "안전한 위치에서 벗어났어요. 자동으로 돌아갈게요." → 대상 브랜치(main 또는 master)가 존재할 때만git checkout main (또는 master) 실행
Merge Conflict (UU, AA 등): 충돌 파일 목록을 보여주고, 채팅 번호형 선택지로 해결 방법을 묻는다 (shared/questioning-policy.md §A):text
두 사람이 같은 파일의 같은 부분을 동시에 고쳐서 충돌이 생겼어요.
충돌 파일: {파일 목록}
질문: 어떻게 할까요?
1. 내가 수정한 걸로 유지 — 내 변경 내용을 사용해요
2. 상대방이 수정한 걸로 유지 — 상대방의 변경 내용을 사용해요
3. 문장으로 직접 수정 요청
선택에 따라:
"내 거 유지": git checkout --ours {파일} → git add {파일}
"상대방 거 유지": git checkout --theirs {파일} → git add {파일}
충돌 해결 후 "저장해줘"로 다음 단계를 안내한다.
Step 3: 상태 번역
git status --porcelain 결과를 자연어로 번역한다:
Porcelain 코드
자연어 번역
M (modified)
수정됨
A (added)
새로 추가됨
D (deleted)
삭제됨
R (renamed)
이름 바뀜
?? (untracked)
새 파일 (아직 Git이 모르는 파일)
Step 4: 결과 출력
상황별 출력 형식:
변경 사항이 있을 때
현재 상태:
변경된 파일 3개:
- index.html (수정됨)
- style.css (새 파일)
- old-logo.png (삭제됨)
아직 저장(Commit)하지 않은 상태예요.
저장하려면 "저장해줘"라고 하세요.
저장은 했지만 올리지 않았을 때
현재 상태:
저장(Commit)은 되어 있지만, 아직 내 컴퓨터에만 있어요.
GitHub에 올리지 않은 저장이 2개 있어요:
- "로고 변경" (10분 전)
- "메인 페이지 수정" (30분 전)
클라우드에 올리려면 "올려줘"라고 하세요.
모든 게 깨끗할 때
현재 상태: 깨끗해요!
모든 변경 내용이 저장되고 GitHub에도 올라가 있어요.
마지막 저장: "로고 변경" (10분 전)
원격 연결이 없을 때
현재 상태:
이 폴더는 Git으로 관리되고 있지만, GitHub에 연결되어 있지 않아요.
연결하려면 "깃 시작해줘"라고 하세요.
Show full SKILL.md (183 more words)Show less
Step 5: Branch 상태 안내
현재 브랜치 정보도 자연어로 번역한다.
bash
git branch --show-current
git log --oneline origin/{branch}..HEAD 2>/dev/null # 올리지 않은 저장
git log --oneline HEAD..origin/{branch} 2>/dev/null # 내려받지 않은 변경
브랜치 상태별 출력
main/master 브랜치에 있을 때
현재 위치: main (기본 브랜치)
별도 브랜치에 있을 때
현재 위치: feature/add-login (작업 브랜치)
기본 브랜치(main)에서 분기된 상태예요.
올리지 않은 저장이 있을 때
GitHub에 올리지 않은 저장이 2개 있어요:
- "로그인 기능 추가" (10분 전)
- "스타일 수정" (30분 전)
GitHub에 새 변경이 있을 때
GitHub에 아직 내려받지 않은 변경이 1개 있어요.
최신 상태로 맞추려면 "내려받아줘"라고 하세요.
Step 6: Stash 상태 확인
bash
git stash list
임시 저장(stash)이 있으면 안내한다:
임시로 보관 중인 변경 내용이 1개 있어요:
- "작업 중이던 헤더 수정" (3일 전)
복원하려면 알려주세요.
복합 상태 처리
여러 상태가 동시에 존재할 때 우선순위에 따라 가장 중요한 것을 먼저 보여준다.
우선순위
충돌 (즉시 해결 필요)
Detached HEAD (위험한 상태)
변경 사항 있음 (저장 권유)
저장했지만 안 올림 (올리기 권유)
GitHub 새 변경 (내려받기 권유)
깨끗함 (모든 게 정상)
복합 상태 출력 예시
현재 상태:
⚠ 변경된 파일 2개:
- index.html (수정됨)
- style.css (새 파일)
또한, GitHub에 올리지 않은 이전 저장이 1개 있어요:
- "로고 변경" (1시간 전)
먼저 "저장해줘"로 현재 변경을 저장한 뒤,
"올려줘"로 모든 저장을 GitHub에 올리세요.
다음 행동 안내
모든 상태 결과 끝에 다음 행동을 안내한다:
상태
안내
변경 사항 있음
"저장하려면 '저장해줘'라고 하세요"
저장만 됨
"GitHub에 올리려면 '올려줘'라고 하세요"
깨끗함
"모든 변경이 저장되고 올라가 있어요"
충돌
충돌 해결 선택지 제시
GitHub 새 변경
"최신 내용을 받으려면 '내려받아줘'라고 하세요"
원격 미연결
"'깃 시작해줘'로 GitHub에 연결하세요"
여러 상태가 겹치면 위 우선순위에 따라 가장 시급한 것부터 안내하되, 전체 흐름을 함께 알려준다.
Git Teacher Status next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Git Teacher Status compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Git Teacher Status this skillfivetaku/gptaku-plugins-codex
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
Runs a multi-agent deep research workflow in seven phases, from scoping questions to a final report with source triangulation, state tracking and quality ratings.
This skill should be used when the user asks to "스킬 만들어줘", "에이전트 만들어줘", "커맨드 만들어줘", "스킬러들의 수다", "수다", "Codex 스킬 만들어줘", "이 스킬 분석해줘", "이 스킬 개선해줘", "skill builder", "make a skill", "create a skill"…
A skill your agent uses when the user runs /dd or /ㅇㅇ (Hangul IME alias — typing "dd" in Korean IME produces "ㅇㅇ") to act on the current OS clipboard (text or image) without pasting it into chat.
Fetch and explain official documentation for any library, framework, API, or service using an llms.txt-first strategy — triggers on "How do I…", "What is…", "How does X work", "Best practice for…"…
Translates current Git status into plain-language explanations for non-developers. Git Teacher Status is an agent skill from fivetaku/gptaku-plugins-codex. Translates current Git status into plain-language explanations for non-developers.
When should I use Git Teacher Status?
Git Teacher Status fits situations like: tasks that involve Git workflow; tasks that involve Plain language and style rules.
How do I install Git Teacher Status in Claude Code?
Run `npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-status -a claude-code`. Or copy the skill folder (plugins/git-teacher-codex/skills/git-teacher-status in fivetaku/gptaku-plugins-codex) into .claude/skills/git-teacher-status in your project. Claude Code loads it when a task matches its description.
How do I install Git Teacher Status in Codex?
Run `npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-status -a codex`. Or copy the skill folder (plugins/git-teacher-codex/skills/git-teacher-status in fivetaku/gptaku-plugins-codex) into .agents/skills/git-teacher-status in your project. Codex loads it when a task matches its description.
Can I use Git Teacher Status in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-teacher-status, .gemini/skills/git-teacher-status, .github/skills/git-teacher-status and .opencode/skills/git-teacher-status in your project.
What does Git Teacher Status need to run?
Going by SKILL.md and its folder, Git Teacher Status needs the command-line tools its instructions call (git).
Does Git Teacher Status access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Git Teacher Status safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Git Teacher Status use?
Git Teacher Status is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Git Teacher Status use?
About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Git Teacher Status?
Skills that share tags, products or a category with Git Teacher Status: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Release Bump (jamiepine/voicebox, 57k stars) and Creating Description For Gh PR (redis/jedis, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Git Teacher Status?
fivetaku (a GitHub user) maintains it in fivetaku/gptaku-plugins-codex, which has 128 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on September 8, 2026.
Source: fivetaku/gptaku-plugins-codex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
