manage-git-branches
について
このClaude Skillは、開発者が機能開発、修正、クリーンアップのためのGitブランチを管理するのを支援します。上流リポジトリとの同期やマージ済みブランチの安全な削除を含む、ブランチの作成、切り替え、スタッシュを使用した安全なプラクティスを扱います。新規作業の開始時、タスク切り替え時、またはmainブランチとの同期維持にご利用ください。
クイックインストール
Claude Code
推奨npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/manage-git-branchesこのコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします
ドキュメント
Manage Git Branches
Create, switch, sync, clean up branches per consistent naming.
Use When
- Start new feature / bug fix
- Switching tasks on diff branches
- Keep feature branch up-to-date w/ main
- Clean up after merging PRs
- List + inspect branches
In
- Req: Repo w/ ≥1 commit
- Opt: Naming convention (default:
type/description) - Opt: Base branch (default:
main) - Opt: Remote name (default:
origin)
Do
Step 1: Create Feature Branch
Consistent naming:
| Prefix | Purpose | Example |
|---|---|---|
feature/ | New functionality | feature/add-weighted-mean |
fix/ | Bug fix | fix/null-pointer-in-parser |
docs/ | Documentation | docs/update-api-reference |
refactor/ | Code restructuring | refactor/extract-validation |
chore/ | Maintenance | chore/update-dependencies |
test/ | Test additions | test/add-edge-case-coverage |
# Create and switch to a new branch from main
git checkout -b feature/add-weighted-mean main
# Or using the newer switch command
git switch -c feature/add-weighted-mean main
→ New branch created + checked out. git branch shows branch w/ asterisk.
If err: Base branch doesn't exist locally → fetch first: git fetch origin main && git checkout -b feature/name origin/main.
Step 2: Track Remote Branches
Setup tracking when pushing new branch first time:
# Push and set upstream tracking
git push -u origin feature/add-weighted-mean
# Check tracking relationship
git branch -vv
Check out remote branch someone else created:
git fetch origin
git checkout feature/their-branch
# Git auto-creates a local tracking branch
→ Local tracks remote. git branch -vv shows upstream.
If err: Auto-tracking fails → manually: git branch --set-upstream-to=origin/feature/name feature/name.
Step 3: Switch Branches Safely
Before switch → working tree clean:
# Check for uncommitted changes
git status
Changes exist → commit or stash:
# Option 1: Commit work in progress
git add <files>
git commit -m "wip: save progress on validation logic"
# Option 2: Stash changes temporarily
git stash push -m "validation work in progress"
# Switch branches
git checkout main
# Later, restore stashed changes
git checkout feature/add-weighted-mean
git stash pop
List + manage stashes:
# List all stashes
git stash list
# Apply a specific stash (without removing it)
git stash apply stash@{1}
# Drop a stash
git stash drop stash@{0}
→ Switch succeeds. Working tree reflects target. Stashed changes recoverable.
If err: Switch blocked by uncommitted changes → stash or commit first. git stash can't stash untracked files unless git stash push -u.
Step 4: Sync w/ Upstream
Keep feature branch up-to-date w/ base:
# Fetch latest changes
git fetch origin
# Rebase onto latest main (preferred — keeps linear history)
git rebase origin/main
# Or merge main into your branch (creates merge commit)
git merge origin/main
→ Branch has latest from main. No conflicts, or resolved (see resolve-git-conflicts).
If err: Rebase conflicts → resolve each + git rebase --continue. Too complex → abort w/ git rebase --abort + try git merge origin/main.
Step 5: Clean Up Merged Branches
After PRs merged → remove stale:
# Delete a local branch that has been merged
git branch -d feature/add-weighted-mean
# Delete a local branch (force, even if not merged)
git branch -D feature/abandoned-experiment
# Delete a remote branch
git push origin --delete feature/add-weighted-mean
# Prune remote-tracking references for deleted remote branches
git fetch --prune
→ Merged branches removed locally + remotely. git branch shows only active.
If err: git branch -d refuses unmerged. If merged via squash merge on GitHub → Git may not recognize as merged. Use git branch -D if certain work preserved.
Step 6: List + Inspect
# List local branches
git branch
# List all branches (local and remote)
git branch -a
# List branches with last commit info
git branch -v
# List branches merged into main
git branch --merged main
# List branches NOT yet merged
git branch --no-merged main
# See which remote branch each local branch tracks
git branch -vv
→ Clear view of all branches, status, tracking.
If err: Remote branches appear stale → git fetch --prune → clean up refs to deleted remotes.
Check
- Branch names follow agreed convention
- Feature branches from correct base
- Local branches track remotes
- Merged cleaned up (local + remote)
- Working tree clean before switches
- Stashes not left orphaned
Traps
- Work on main directly: Always create feature branch. Committing directly to main → hard to create PRs + collaborate.
- Forget fetch before branching: Creating from stale local main → start behind. Always
git fetch originfirst. - Long-lived branches: Weeks-long → accumulate conflicts. Sync freq + keep short-lived.
- Orphaned stashes:
git stash= temporary storage. Don't rely for long-term. Commit / branch instead. - Delete unmerged work:
git branch -Ddestructive. Double-check w/git log branch-namebefore force-delete. - Not pruning: Remote branches deleted on GitHub still appear locally until
git fetch --prune.
→
commit-changes— committing work on branchescreate-pull-request— opening PRs from feature branchesresolve-git-conflicts— handling conflicts during syncconfigure-git-repository— repo setup + branch strategy
GitHub リポジトリ
関連スキル
content-collections
メタこのスキルは、Content Collections(Markdown/MDXファイルを型安全なデータコレクションに変換するTypeScriptファーストのツール)の本番環境でテストされた設定を提供します。Zodバリデーションによる型安全性を実現し、ブログ、ドキュメントサイト、コンテンツ重視のVite + Reactアプリケーション構築時にご利用ください。Viteプラグインの設定、MDXコンパイルから、デプロイ最適化、スキーマバリデーションまで、すべてを網羅しています。
polymarket
メタこのスキルは、開発者がPolymarket予測市場プラットフォームを活用したアプリケーション構築を可能にします。API統合による取引や市場データの取得に加え、WebSocketを介したリアルタイムデータストリーミングにより、ライブ取引や市場活動を監視できます。取引戦略の実装や、ライブ市場更新を処理するツールの作成にご利用ください。
creating-opencode-plugins
メタこのスキルは、開発者がコマンド、ファイル、LSP操作など25種類以上のイベントタイプにフックするOpenCodeプラグインを作成することを支援します。JavaScript/TypeScriptモジュール向けに、プラグイン構造、イベントAPI仕様、および実装パターンを提供します。カスタムイベント駆動ロジックでOpenCode AIアシスタントのライフサイクルをインターセプト、監視、または拡張する必要がある場合にご利用ください。
sglang
メタSGLangは、高性能なLLMサービングフレームワークであり、RadixAttentionプレフィックスキャッシュを活用したJSON、正規表現、エージェントワークフロー向けの高速で構造化された生成を特長とします。特にプレフィックスが繰り返されるタスクにおいて、大幅に高速な推論を実現し、複雑な構造化出力やマルチターン対話に最適です。制約付きデコードが必要な場合や、広範なプレフィックス共有を伴うアプリケーションを構築する場合は、vLLMなどの代替案ではなくSGLangを選択してください。
