Menu
Rebase current branch onto latest main/master.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | git-sync-branch |
| description | Rebase current branch onto latest main/master. |
| allowed-tools | ["Bash(git branch *)","Bash(git fetch origin main)","Bash(git fetch origin master)","Bash(git rebase origin/main)","Bash(git rebase origin/master)","Bash(git rebase --abort)"] |
git branch --list main master (main ์ฐ์ ). git remote show origin ์ฌ์ฉ ๊ธ์ง.git fetch origin <branch> โ git rebase origin/<branch>git rebase --abort ํ ์ ์ ์๊ฒ ๋ณด๊ณ . ์๋ resolve ๊ธ์ง.Improve comments and docs so they capture non-obvious intent, caller-visible contracts, invariants, and why-context; prune comments that only restate code. Use whenever writing or modifying code (any new or edited source file), not just on explicit cleanup requests. Triggers on "์ฃผ์ ์ ๋ฆฌ", "์ฃผ์ ๋ค๋ฌ๊ธฐ", "comment cleanup", "prune comments", "์๋ ์ ๋ฆฌ", "clarify code intent", "intent comments", "contract docs", "API contract comments".
Write or update Java class-level Javadoc that documents responsibility, caller-visible boundaries, invariants, and thread-safety. Use when modifying API-facing or boundary-owning Java types, SPI and extension types, factories or coordinators that choose policy or workflow, abstract/interface contracts, or behavior-bearing core domain types whose responsibility, invariants, lifecycle, or threading are not obvious.
Write or update Java method-level Javadoc that documents caller-visible contracts, preconditions, postconditions, exceptions, externally visible side effects, and performance constraints. Use when modifying API, SPI, extension, or reused internal Java methods whose caller-visible or durable internal contract is non-obvious or not encoded by signatures, annotations, validation, or inherited documentation.
Write or update Java package-info.java documentation that defines package responsibility, durable boundaries, optional non-responsibilities, package-wide invariants, and extension points. Use when adding, renaming, moving, or splitting packages; changing responsibility across package boundaries; or creating/updating package-info.java for API-facing or shared packages with durable ownership rules.
Write unit tests following London School (mockist) TDD style.
Checkout main/master, pull latest, prune stale remotes.