Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Automated review request workflow — handles branch creation, commit, push, and PR creation as one step.
Install Git Teacher Review
$ npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-review --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-review .claude/skills/git-teacher-review && 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-review" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-review into .claude/skills/git-teacher-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-review", 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-reviewType 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-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-review --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-review .agents/skills/git-teacher-review && 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-review" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-review into .agents/skills/git-teacher-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-review", 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-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-review --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-review .cursor/skills/git-teacher-review && 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-review" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-review into .cursor/skills/git-teacher-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-review", 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-review--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-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex git-teacher-review --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-review .gemini/skills/git-teacher-review && 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-review" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-review into .gemini/skills/git-teacher-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-review", 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-reviewInstalls 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-review -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-review .github/skills/git-teacher-review && 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-review" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-review into .github/skills/git-teacher-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-review", 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-review -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-review --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-review .opencode/skills/git-teacher-review && 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-review" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-review into .opencode/skills/git-teacher-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-teacher-review", 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-review- GitHub stars
- 128
- Token cost
- ~1.3k tokens
- SKILL.md length
- 554 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
Automated review request workflow — handles branch creation, commit, push, and PR creation as one step.
- Works in 8 steps: 병렬 상태 수집 → 안전 검사 → 작업 설명 요청 → …
- Tasks that involve Git workflow
- SKILL.md covers 실행 순서, 이미 별도 branch에 있는 경우, 충돌 해결 and 오류 처리, plus 1 more section
- Calls git and gh; reaches github.com
What it does
Git Teacher Review is an agent skill from fivetaku/gptaku-plugins-codex. Automated review request workflow — handles branch creation, commit, push, and PR creation as one step. Hides Git branch jargon from users and presents it as "a safe workspace to show your teammates." Korean triggers — "PR 만들어줘", "검토 요청", "리뷰 요청", "수정 제안", "팀원한테 보여주고 싶어", "확인 요청". English triggers — "create PR", "pull request", "request review", "show teammates".
Its SKILL.md is about 1.3k 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 Development, covering Git workflow and Pull requests. It works with Git. 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 Pull requests
Example prompts
- “a safe workspace to show your teammates.”
- “PR 만들어줘”
- “. English triggers —”
- “/git-teacher-review”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
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
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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 Review loads about 1.3k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 554 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). 554 words, ~1,265 tokens.
Download SKILL.mdSave it as
.claude/skills/git-teacher-review/SKILL.md (or your agent's skills folder).- name
- git-teacher-review
- description
- Automated review request workflow — handles branch creation, commit, push, and PR creation as one step. Hides Git branch jargon from users and presents it as "a safe workspace to show your teammates." Korean triggers — "PR 만들어줘", "검토 요청", "리뷰 요청", "수정 제안", "팀원한테 보여주고 싶어", "확인 요청". English triggers — "create PR", "pull request", "request review", "show teammates".
검토 요청하기 — Phase 5 (바르다 깃선생 — Codex)
Branch 생성 → Commit → Push → PR 생성을 자동으로 처리한다. Branch 개념은 사용자에게 숨기고 "안전한 작업 공간"으로 설명한다.
설명·교육 시
git-teacher-help의 §교육 원칙(shared/questioning-policy.md§3 Teaching)을 따른다. "검토 요청(PR)"은 Google Docs "수정 제안" 모드 비유로 설명한다. 겁먹은 초보면 원샷 금지(§2a), 그냥 PR만 원하면 강의 없이 진행(§2c). Codex CLI에는 객관식 카드 UI가 없다. 결정이 필요한 곳은shared/questioning-policy.md§A의 채팅 번호형 선택지 블록으로 묻는다.
실행 순서
Step 1: 병렬 상태 수집
다음 명령을 병렬로(가능한 한 함께) 실행한다:
git rev-parse --is-inside-work-tree # .git 존재 확인
git symbolic-ref --short HEAD # 현재 branch (detached HEAD 감지)
git status --porcelain # 변경 파일 목록
git rev-list --count @{u}..HEAD 2>/dev/null || git rev-list --count HEAD 2>/dev/null # 올리지 않은 commit 수 (upstream 없으면 전체 commit 수로 대체)
git remote get-url origin 2>/dev/null # 원격 저장소 URL
gh auth status 2>&1 # GitHub CLI 로그인 상태Step 2: 안전 검사
.git없음: "여기는 Git 프로젝트 폴더가 아니에요. '깃 시작해줘'로 먼저 설정하세요." → 중단- Detached HEAD: "안전한 위치에서 벗어났어요. 자동으로 돌아갈게요." →
git checkout main(또는master) 실행 후 재시도 - 원격 저장소 없음: "GitHub에 연결되어 있지 않아요. '깃 시작해줘'로 먼저 설정하세요." → 중단
- gh 미로그인: "GitHub CLI에 로그인되어 있지 않아요. '깃 시작해줘'로 설정하세요." → 중단
- Merge Conflict (
UU,AA등 감지 시): 충돌 해결 안내 (아래 "충돌 해결" 섹션 참조) → 중단 - 변경 사항 판단: 아래 두 조건을 모두 확인한다:
git status --porcelain결과 (수정된 파일 존재 여부)git rev-list --count @{u}..HEAD결과 (올리지 않은 commit 존재 여부; upstream 미설정 시 전체 commit 수로 대체)- 둘 다 비어있으면: "변경된 파일도 없고, 올리지 않은 저장도 없어요. 파일을 수정한 뒤 다시 시도하세요." → 중단
- 수정된 파일은 없지만 미전송 commit이 있으면: 이미 저장(save)된 내용으로 PR 진행 (Step 5에서 commit 스킵)
- 이미 main/master가 아닌 branch에 있음: 현재 branch에서 그대로 진행 (새 branch 생성 스킵)
Step 3: 작업 설명 요청
먼저 비유로 안심시킨다:
검토 요청(PR)을 만들어볼게요.
Google Docs에서 "수정 제안" 모드 아시죠?
원본은 그대로 두고, "이렇게 바꾸면 어떨까요?" 하고 보내는 거예요.그다음 채팅 번호형 선택지로 묻는다 (shared/questioning-policy.md §A) — diff나 최근 commit에서 설명을 추론할 수 있으면 묻지 않고 추론안을 제시하고 확인만 받는다:
질문: 어떤 작업을 했는지 한 줄로 적어주세요.
1. 직접 입력 — 한 줄로 알려주세요 (예: "메인 페이지 디자인 변경", "오타 수정")
2. 자동 생성 — 변경 내용을 분석해서 설명을 자동으로 만들어요
3. 문장으로 직접 수정 요청Step 4: Branch 생성 (사용자에게 숨김)
현재 branch가 main 또는 master인 경우에만 새 branch를 생성한다:
git checkout -b {slug}/{date}Branch 이름 규칙:
- 사용자 입력을 slug화: "메인 페이지 디자인 변경" →
main-page-design - 날짜 추가:
main-page-design/0222 - 한국어는 영어로 간단히 변환하거나 로마자화
사용자에게는: "안전한 작업 공간을 만들었어요. 여기서는 마음껏 수정해도 원본에 영향이 없어요."
이미 저장된(commit) 내용을 새 branch로 옮기는 경우:
main에서 이미 commit된 상태라면, branch를 만든 뒤 main의 commit을 되돌려야 한다.
미전송 commit 수는 Step 1에서 수집한 git rev-list --count 결과를 사용한다:
git checkout -b {slug}/{date} # 새 branch 생성 (commit 포함)
git checkout main # main으로 잠시 돌아감
git reset --soft HEAD~{미전송 commit 수} # main의 commit 되돌림 (staging area에 남음)
git checkout {slug}/{date} # 다시 작업 branch로주의: 이 과정에서 기존 개별 commit 메시지들은 하나로 합쳐진다 (squash 효과). 비개발자에게는 오히려 깔끔한 결과를 제공하므로 의도된 동작이다. (여기서 쓰는
reset --soft는 변경 내용을 staging에 남기는 안전한 방식이다 —reset --hard가 아니다.)
Show full SKILL.md (188 more words)Show less
Step 5: Commit + Push
수정된 파일이 있는 경우에만 commit한다 (이미 저장된 경우 스킵):
git add -A # 수정된 파일이 있을 때만
git commit -m "사용자가 입력한 작업 설명" # 수정된 파일이 있을 때만
git push origin HEADStep 6: PR 생성
gh pr create --title "사용자가 입력한 작업 설명" --body "$(cat <<'EOF'
## 변경 내용
{사용자가 입력한 작업 설명}
---
Created by 바르다 깃선생
EOF
)"Step 7: main으로 복귀
PR 생성 후, 안전하고 원래 main/master가 있었던 경우에만 main branch로 돌아간다:
git checkout mainStep 8: 영수증 출력
검토 요청 완료!
링크: https://github.com/username/my-project/pull/1
이 링크를 팀원에게 보내면, 변경 내용을 확인하고
"좋아요, 반영해주세요" 하고 승인할 수 있어요.
지금은 원래 위치(main)로 돌아온 상태예요.
새로운 작업을 시작하려면 파일을 수정한 뒤 "저장해줘"라고 하세요.이미 별도 branch에 있는 경우
Step 2에서 현재 branch가 main/master가 아닌 경우:
- Step 4(branch 생성)를 스킵
- 현재 branch에서 바로 commit → push → PR 생성 진행
- "이미 작업 공간에 있어서, 바로 검토 요청을 만들게요."
충돌 해결
Merge Conflict 감지 시 충돌 파일 목록을 보여주고, 채팅 번호형 선택지로 묻는다 (shared/questioning-policy.md §A):
두 사람이 같은 파일의 같은 부분을 동시에 고쳐서 충돌이 생겼어요.
충돌 파일: {파일 목록}
질문: 어떻게 할까요?
1. 내가 수정한 걸로 유지 — 내 변경 내용을 사용해요
2. 상대방이 수정한 걸로 유지 — 상대방의 변경 내용을 사용해요
3. 문장으로 직접 수정 요청선택에 따라:
- "내 거 유지":
git checkout --ours {파일}→git add {파일} - "상대방 거 유지":
git checkout --theirs {파일}→git add {파일}
충돌 파일이 여러 개일 경우 파일 목록을 보여주고 일괄 처리한다.
오류 처리
- PR 이미 존재: "이 작업 공간의 검토 요청이 이미 있어요." → 기존 PR URL 안내 (새로 만들지 않는다)
- push 실패: upload 스킬의 오류 처리와 동일하게 안내
- gh pr create 실패: "검토 요청 생성에 실패했어요." →
gh auth status재확인 안내
Safety
git reset --hard는 사용하지 않는다 (branch 이동 시에도reset --soft만 사용).- 사용자가 명시적으로 요청하지 않으면 commit된 히스토리를 재작성하지 않는다.
- 같은 branch에 이미 PR이 있으면 새로 만들지 않고 기존 PR URL을 보여준다.
© 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
Just SKILL.md in plugins/git-teacher-codex/skills/git-teacher-review of fivetaku/gptaku-plugins-codex.
Open the folder on GitHubat commit d3b47fc
Compare with similar skills
Git Teacher Review 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 Review this skillfivetaku/gptaku-plugins-codex | 128 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | 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 | |
| Git Branch Namingmakeplane/plane | 61k | — | ~594 | Automated safety check: Pass | AGPL-3.0 | |
| Creating Description For Gh PRredis/jedis | 12k | — | ~838 | Automated safety check: Pass | MIT |
Similar skills
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.
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.
Git Branch Naming
makeplane/plane
Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.
- 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.
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
Works with
Categories
Questions about Git Teacher Review
What does Git Teacher Review do?
Automated review request workflow — handles branch creation, commit, push, and PR creation as one step. Git Teacher Review is an agent skill from fivetaku/gptaku-plugins-codex. Automated review request workflow — handles branch creation, commit, push, and PR creation as one step.
When should I use Git Teacher Review?
Git Teacher Review fits situations like: tasks that involve Git workflow; tasks that involve Pull requests.
How do I install Git Teacher Review in Claude Code?
Run `npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-review -a claude-code`. Or copy the skill folder (plugins/git-teacher-codex/skills/git-teacher-review in fivetaku/gptaku-plugins-codex) into .claude/skills/git-teacher-review in your project. Claude Code loads it when a task matches its description.
How do I install Git Teacher Review in Codex?
Run `npx skills add fivetaku/gptaku-plugins-codex --skill git-teacher-review -a codex`. Or copy the skill folder (plugins/git-teacher-codex/skills/git-teacher-review in fivetaku/gptaku-plugins-codex) into .agents/skills/git-teacher-review in your project. Codex loads it when a task matches its description.
Can I use Git Teacher Review 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-review -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-review, .gemini/skills/git-teacher-review, .github/skills/git-teacher-review and .opencode/skills/git-teacher-review in your project.
What does Git Teacher Review need to run?
Going by SKILL.md and its folder, Git Teacher Review needs the command-line tools its instructions call (git and gh).
Does Git Teacher Review access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Git Teacher Review 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 Review use?
Git Teacher Review 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 Review use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 Review?
Skills that share tags, products or a category with Git Teacher Review: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and Git Branch Naming (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Git Teacher Review?
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.