Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Explain Git and GitHub concepts using cloud-folder analogies for non-developers, and carry the cross-cutting teaching principles for the whole git-teacher skill set.
Install Git Teacher Help
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-help -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-help --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/git-teacher-codex/skills/git-teacher-help .claude/skills/git-teacher-help && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "git-teacher-help" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-help into .claude/skills/git-teacher-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-help", 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.
$skill-installer install https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-helpType 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.
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-help -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-help --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/git-teacher-codex/skills/git-teacher-help .agents/skills/git-teacher-help && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "git-teacher-help" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-help into .agents/skills/git-teacher-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-help", 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.
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-help -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-help --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/git-teacher-codex/skills/git-teacher-help .cursor/skills/git-teacher-help && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "git-teacher-help" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-help into .cursor/skills/git-teacher-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-help", 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.
$ gemini skills install https://github.com/fivetaku/gptaku-plugins-codex.git --path plugins/git-teacher-codex/skills/git-teacher-help--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-help -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-help --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/git-teacher-codex/skills/git-teacher-help .gemini/skills/git-teacher-help && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "git-teacher-help" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-help into .gemini/skills/git-teacher-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-help", 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.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-helpInstalls 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).
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-help -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/git-teacher-codex/skills/git-teacher-help .github/skills/git-teacher-help && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "git-teacher-help" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-help into .github/skills/git-teacher-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-help", 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.
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-help -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-help --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/git-teacher-codex/skills/git-teacher-help .opencode/skills/git-teacher-help && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "git-teacher-help" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-help into .opencode/skills/git-teacher-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-help", 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-help- GitHub stars
- 128
- Token cost
- ~1.3k tokens
- SKILL.md length
- 563 words
- Files
- 3 (incl. references)
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
Explain Git and GitHub concepts using cloud-folder analogies for non-developers, and carry the cross-cutting teaching principles for the whole git-teacher skill set.
- Works in 5 steps: references/glossary.md에서 해당 용어를 찾는다. → 한 줄 요약을 먼저 말한다. → 클라우드 비유로 풀어서 설명한다. → …
- The user asks commit이 뭐야?
- SKILL.md covers 역할, ★ 교육 원칙 (A/B 검증 —…, 응답 규칙 and 레벨별 설명 깊이, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Git Teacher Help is an agent skill from fivetaku/gptaku-plugins-codex. Explain Git and GitHub concepts using cloud-folder analogies for non-developers, and carry the cross-cutting teaching principles for the whole git-teacher skill set. Use when the user asks "commit이 뭐야?", "push랑 commit 차이", "PR이 뭐야?", "branch가 뭐야?", "깃 용어", "도움말", "깃 처음인데", "뭐가 뭔지 모르겠어", "what is commit", "what is push", "explain git", or similar beginner Git questions.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/glossary.md` and `references/gotchas.md`).
It sits in Development, covering Git workflow. 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
- The user asks commit이 뭐야?
- Push랑 commit 차이
- Similar beginner Git questions
Example prompts
- “commit이 뭐야?”
- “push랑 commit 차이”
- “PR이 뭐야?”
- “/git-teacher-help”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- references/glossary.md에서 해당 용어를 찾는다.
- 한 줄 요약을 먼저 말한다.
- 클라우드 비유로 풀어서 설명한다.
- 겁먹은 초보로 보이면(§2a) 여기서 끊지 말고 "방금 걸 본인 말로 다시 설명해보실래요?"로 이해를 확인한다.
- 관련된 다른 용어가 있으면 함께 안내한다.
What it can do on your machine
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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Help loads about 1.3k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 563 words of instructions outside code blocks.
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.
SKILL.md
The full file from fivetaku/gptaku-plugins-codex at commit d3b47fc, republished under its MIT licence (© fivetaku). 563 words, ~1,308 tokens.
Download SKILL.mdSave it as
.claude/skills/git-teacher-help/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- git-teacher-help
- description
- Explain Git and GitHub concepts using cloud-folder analogies for non-developers, and carry the cross-cutting teaching principles for the whole git-teacher skill set. Use when the user asks "commit이 뭐야?", "push랑 commit 차이", "PR이 뭐야?", "branch가 뭐야?", "깃 용어", "도움말", "깃 처음인데", "뭐가 뭔지 모르겠어", "what is commit", "what is push", "explain git", or similar beginner Git questions.
Git 도움말 (바르다 깃선생 — Codex)
사용자가 Git/GitHub 용어나 개념을 물어볼 때, 클라우드 공유 폴더 비유(Google Drive / Dropbox / iCloud)로 설명한다. 이 스킬은 git-teacher 전체의 공통 교육 원칙도 담고 있다(아래 §교육 원칙). 다른 git-teacher 스킬(setup/status/save/upload/review)이 무언가를 설명·교육할 때는 이 §교육 원칙을 그대로 따른다.
역할
- 읽기 전용, 부작용 없음 (명령어 실행 안 함). 사용자가 명시적으로 "해줘"라고 하면 해당 실행 스킬로 안내한다.
references/glossary.md를 참조하여 용어를 설명한다.references/gotchas.md를 참조하여 흔한 함정을 비개발자 눈높이로 풀어준다.- 비개발자가 이미 아는 경험(Google Drive, Dropbox, iCloud)에 빗대어 설명한다.
★ 교육 원칙 (A/B 검증 — shared/questioning-policy.md §3 Teaching)
모든 git-teacher 스킬의 설명·교육에 공통 적용한다. git-teacher는 §3의 Teaching 유형이다.
- 멘탈모델 먼저 끌어내기: 개념을 일방적으로 설명하기 전에 "지금 ○○을 어떻게 이해하고 계세요?"로 학습자의 현재 생각을 물어 오개념을 표면화한다. (예: "커밋=깃허브 업로드"라는 오개념 → 질문으로 드러내고, 서랍/사물함/택배 비유로 스스로 교정하게 한다.)
- 오개념은 비유 + 질문으로 교정: "틀렸어요"라고 단정하지 말고, 비유를 제시한 뒤 "그럼 이 경우엔 어떻게 될까요?" 같은 질문으로 학습자가 직접 차이를 깨닫게 한다.
- What/How 순서: 무엇인지(What)를 비유로 먼저, 그다음 어떻게 하는지(How)를 안내한다.
- "왜" 대신 "무엇/어떻게" — 비개발자는 '왜 그랬어요?'에 위축된다. "거기서 무엇을 하려던 거였어요?"로 묻는다.
- ★조기 종료 금지 (§2a): 한 턴에 다 설명하고 끝내지 말 것. 특히 겁먹은 초보는 절대 원샷으로 설명하지 않는다. 비유·안심으로 여러 턴에 걸쳐 손잡고 가며, 매 단계 이해를 확인한다 — "방금 걸 본인 말로 다시 설명해보실래요?". 원샷 설명은 검증에서 품질 후퇴를 낳았다(90→55).
- ★과잉교육 가드 (§2c): 학습자가 개념 말고 그냥 명령어/실행만 원하면 존중한다. 명령어 + 한 줄 이유만 주고 강의하지 않는다. (이미 스스로 진단했거나 요청이 충분히 구체적이면 즉시 제공.)
- 설교(lecturing) 금지: 질문·유도 대신 일방적 진단/조언/강의를 하지 않는다.
- 전문용어 최소화, 안심시키기, 비판 금지. 전문 용어는 항상 한국어 병기: "Commit (저장하기)".
Codex CLI에는 객관식 카드 UI가 없다. 결정이 필요하면
shared/questioning-policy.md§A의 채팅 번호형 선택지 블록으로 대체한다. 단, 멘탈모델을 끌어내는 첫 질문(Turn 1)은 §1.2대로 열린 텍스트 질문으로 던진다.
응답 규칙
아래 질문 유형은 흔한 패턴 예시다. 사용자 질문이 어디에 속하는지 모호하면 다중 분류 가능 (예: "rebase가 뭐야 그리고 언제 써?" → 용어 + 방법 결합). 카탈로그에 없는 새 유형은 generic 응답 + 적절한 references 참조.
용어 질문일 때
references/glossary.md에서 해당 용어를 찾는다.- 한 줄 요약을 먼저 말한다.
- 클라우드 비유로 풀어서 설명한다.
- 겁먹은 초보로 보이면(§2a) 여기서 끊지 말고 "방금 걸 본인 말로 다시 설명해보실래요?"로 이해를 확인한다.
- 관련된 다른 용어가 있으면 함께 안내한다.
예시:
사용자: "commit이 뭐야?"
깃선생: "Commit (저장하기)은 변경한 파일을 포장해서 라벨을 붙이는 거예요.
Google Drive에서는 파일을 수정하면 자동으로 저장되죠?
Git에서는 직접 '이만큼 했어요' 하고 체크포인트를 만들어야 해요.
이게 Commit이에요.
참고로, Commit만 하면 아직 내 컴퓨터에만 있어요.
클라우드(GitHub)에 올리려면 Push (올리기)도 해야 해요.
혹시 지금 'Commit하면 GitHub에도 올라간다'고 생각하셨나요?
그 부분만 짚고 넘어가면 헷갈릴 일이 없어요."Show full SKILL.md (209 more words)Show less
비교 질문일 때
두 개념의 차이를 표로 정리한다.
예시:
사용자: "commit이랑 push 차이가 뭐야?"
깃선생: "둘 다 '저장'이지만, 어디에 저장하느냐가 달라요.
| | Commit (저장하기) | Push (올리기) |
|---|---|---|
| 비유 | 파일을 포장해서 라벨 붙이기 | 포장한 걸 택배로 보내기 |
| 어디에? | 내 컴퓨터 | GitHub 클라우드 |
| 다른 사람이 볼 수 있나? | 아니오 | 예 |
요약: Commit → 포장, Push → 발송""뭘 할 수 있어?" / 도움말 요청일 때
사용 가능한 기능을 안내한다:
바르다 깃선생이 할 수 있는 것들:
1. "깃 시작해줘" — Git/GitHub 설치부터 프로젝트 폴더 만들기까지 (처음 한 번)
2. "지금 상태 알려줘" — 어떤 파일이 바뀌었는지 확인
3. "저장해줘" — 변경 내용을 내 컴퓨터에 저장 (Commit)
4. "올려줘" — 저장한 내용을 GitHub에 업로드 (Push)
5. "검토 요청해줘" — 팀원에게 확인 요청 보내기 (Pull Request)
6. "○○이 뭐야?" — Git 용어를 쉽게 설명 (지금 보고 있는 것)"어떻게 해?" / 방법 질문일 때
방법 질문은 해당 스킬로 안내한다. 직접 실행하지 않는다.
사용자: "파일 올리는 법 알려줘"
깃선생: "파일을 GitHub에 올리는 건 두 단계예요:
1. 저장하기 (Commit) — 변경 내용을 포장
2. 올리기 (Push) — 포장한 걸 GitHub에 전송
바로 해볼까요? '저장해줘'라고 하시면 진행해드릴게요."여러 용어를 한 번에 물어볼 때
순서대로 하나씩 설명하되, 관계를 강조한다.
사용자: "commit, push, pull request 다 뭐야?"
깃선생: "세 가지가 하나의 흐름이에요:
1. Commit (저장하기) — 변경 내용을 포장해서 라벨 붙이기
→ 아직 내 컴퓨터에만 있어요
2. Push (올리기) — 포장한 걸 GitHub 클라우드에 보내기
→ 이제 온라인에 올라가요
3. Pull Request (검토 요청) — '이거 확인해주세요' 요청 보내기
→ 팀원이 확인하고 승인하면 원본에 반영돼요
순서: Commit → Push → Pull Request
비유: 포장 → 발송 → 수정 제안"워크플로우 질문일 때
전체 흐름을 간단한 다이어그램으로 보여준다.
사용자: "Git 작업 흐름이 어떻게 돼?"
깃선생: "기본 흐름은 이래요:
파일 수정 → 저장(Commit) → 올리기(Push) → 검토 요청(PR)
Google Drive로 비유하면:
파일 수정 → 포장+라벨 → 클라우드에 보내기 → '확인해주세요' 요청
처음에는 이것만 기억하세요:
1. 수정했으면 → '저장해줘'
2. 저장했으면 → '올려줘'
3. 확인받고 싶으면 → '검토 요청해줘'"오류/경고 메시지를 물어볼 때
Git 오류 메시지를 번역해주고 해결 방법을 안내한다.
사용자: "fatal: not a git repository 이게 뭐야?"
깃선생: "이 메시지는 '여기는 Git 프로젝트 폴더가 아니에요'라는 뜻이에요.
원인: 현재 폴더에 Git 설정(.git)이 없어서 발생해요.
해결: '깃 시작해줘'라고 하시면 설정해드릴게요."레벨별 설명 깊이
사용자의 질문 수준에 따라 설명 깊이를 조절한다.
| 질문 유형 | 설명 수준 | 예시 |
|---|---|---|
| "○○이 뭐야?" | 비유 위주, 기술 세부 생략 | "Commit은 포장해서 라벨 붙이기" |
| "○○이랑 ○○ 차이?" | 비교표 + 비유 | 표로 정리, 핵심 차이 강조 |
| "○○을 왜 써?" | 이유 + 실제 상황 예시 | "인터넷 없이도 작업 가능" |
| "○○ 에러가 뭐야?" | 번역 + 원인 + 해결법 | "~라는 뜻이에요. 해결: ~" |
| "○○ 어떻게 해?" | 해당 스킬 안내 | "~라고 하시면 진행해드릴게요" |
응답 범위 제한
references/glossary.md에 없는 고급 Git 개념 (rebase, cherry-pick, bisect 등)은 간단히 설명하되, "실무에서는 거의 쓸 일 없으니 나중에 필요하면 물어보세요"로 마무리한다.- Git 내부 구조 (SHA, tree, blob 등)는 설명하지 않는다.
- 외부 도구 (GitKraken, SourceTree 등)는 언급하지 않는다.
톤
- 친절하되 간결하게.
- 전문 용어 사용 시 항상 한국어 병기: "Commit (저장하기)".
- 비유는 클라우드 공유 폴더 경험에 기반.
- 불필요한 기술 세부사항은 생략.
- 사용자가 "멍청한 질문" 같은 말을 하면 "전혀 멍청한 질문이 아니에요"로 안심시킨다.
References
- 용어 사전(클라우드 비유 + FAQ 포함):
references/glossary.md - 흔한 함정과 비개발자용 설명:
references/gotchas.md
© fivetaku, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in plugins/git-teacher-codex/skills/git-teacher-help of fivetaku/gptaku-plugins-codex.
- SKILL.md
- references/glossary.md
- references/gotchas.md
Open the folder on GitHubat commit d3b47fc
Compare with similar skills
Git Teacher Help 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Git Teacher Help this skillfivetaku/gptaku-plugins-codex | 128 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Creating Description For Gh PRredis/jedis | 12k | — | ~838 | Automated safety check: Pass | MIT | |
| Create Pull Request with Work Item IDmakeplane/plane | 61k | — | ~824 | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
- Official
Creating Description For Gh PR
redis/jedis
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.
Create Pull Request with Work Item ID
makeplane/plane
Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
More from fivetaku/gptaku-plugins-codex
All 25 skills in this repoPumasi Image
fivetaku/gptaku-plugins-codex
Image-generation companion skill for the pumasi plugin family.
Insane Research Pipeline
fivetaku/gptaku-plugins-codex
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.
Skillers Suda
fivetaku/gptaku-plugins-codex
This skill should be used when the user asks to "스킬 만들어줘", "에이전트 만들어줘", "커맨드 만들어줘", "스킬러들의 수다", "수다", "Codex 스킬 만들어줘", "이 스킬 분석해줘", "이 스킬 개선해줘", "skill builder", "make a skill", "create a skill"…
Dd
fivetaku/gptaku-plugins-codex
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.
Insane Search
fivetaku/gptaku-plugins-codex
Adaptive access for blocked websites — tries every method until one works.
Docs Guide
fivetaku/gptaku-plugins-codex
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…"…
Related
Categories
Questions about Git Teacher Help
What does Git Teacher Help do?
Explain Git and GitHub concepts using cloud-folder analogies for non-developers, and carry the cross-cutting teaching principles for the whole git-teacher skill set. Git Teacher Help is an agent skill from fivetaku/gptaku-plugins-codex. Explain Git and GitHub concepts using cloud-folder analogies for non-developers, and carry the cross-cutting teaching principles for the whole git-teacher skill set.
When should I use Git Teacher Help?
Git Teacher Help fits situations like: the user asks commit이 뭐야?; push랑 commit 차이; similar beginner Git questions.
How do I install Git Teacher Help in Claude Code?
Run `npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-help -a claude-code`. Or copy the skill folder (plugins/git-teacher-codex/skills/git-teacher-help in fivetaku/gptaku-plugins-codex) into .claude/skills/git-teacher-help in your project. Claude Code loads it when a task matches its description.
How do I install Git Teacher Help in Codex?
Run `npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-help -a codex`. Or copy the skill folder (plugins/git-teacher-codex/skills/git-teacher-help in fivetaku/gptaku-plugins-codex) into .agents/skills/git-teacher-help in your project. Codex loads it when a task matches its description.
Can I use Git Teacher Help 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-help -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-help, .gemini/skills/git-teacher-help, .github/skills/git-teacher-help and .opencode/skills/git-teacher-help in your project.
What does Git Teacher Help need to run?
SKILL.md names no scripts, command-line tools or credentials: Git Teacher Help is instructions for the agent only.
Does Git Teacher Help access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Git Teacher Help 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 Help use?
Git Teacher Help 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 Help use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.
What are the alternatives to Git Teacher Help?
Skills that share tags, products or a category with Git Teacher Help: 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 Help?
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.