Guide Git branching strategies, branch naming, and merge operations. Use when: creating branches, merging, pull requests, Git workflow questions. Keywords: branch, merge, PR, pull request, GitFlow, GitHub Flow, 分支, 合併, 工作流程.
指導 Git 分支策略、分支命名与合併操作。 使用时机：建立分支、合併、Pull Request、Git 工作流程問題。 关鍵字：branch, merge, PR, pull request, GitFlow, GitHub Flow, 分支, 合併, 工作流程。
Systematic code review checklist and pre-commit quality gates for PRs. Use when: reviewing pull requests, checking code quality, before committing code. Keywords: review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入.
遵循約定式提交标准格式化提交消息。 使用时机：撰写提交消息、git commit、檢视提交历史。 关鍵字：commit、git、message、conventional、feat、fix、refactor。
遵循約定式提交標準格式化提交訊息。 使用時機：撰寫提交訊息、git commit、檢視提交歷史。 關鍵字：commit、git、message、conventional、feat、fix、refactor。
Follow Git branch and commit naming conventions. Use when creating branches, making commits, or when asked about Git conventions.
指導 Git 分支策略、分支命名與合併操作。 使用時機：建立分支、合併、Pull Request、Git 工作流程問題。 關鍵字：branch, merge, PR, pull request, GitFlow, GitHub Flow, 分支, 合併, 工作流程。
Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, feat, fix, refactor.
引導提交前品质关卡和簽入工作流程。 使用时机：提交程序码、准备提交、品质关卡验证。 关鍵字：commit, checkin, pre-commit, quality gate, git add, 提交, 簽入, 品质关卡.
Safe git commit workflow that prevents commits to main branch. Use when the user asks to "commit changes", "save changes", "git commit", or when completing a task that needs version control. Automatically creates feature branches when on main. NEVER creates pull requests unless explicitly requested by the user.
Remove all Claude/AI authorship references from git history including commit messages, co-authored-by lines, and generated-with markers. Uses git-filter-repo for safe history rewriting.
Branch stratejisi, commit conventions, merge conflict çözümü ve Git best practices rehberi.
Fetches and processes GitHub pull requests waiting for review. Returns fully formatted markdown with PRs grouped by category (Feature/Bug, Chores, Dependency Updates) and sorted by age. Includes metadata like CI status, review status, size metrics, and viewing history. Use when user wants to see their PR review queue.
This skill monitors PR CI checks by polling GitHub status until completion or timeout. Use when the user requests to check CI status, wait for CI to pass, monitor PR checks, or verify build status. Applicable for queries like "check my CI", "wait for CI to pass", "is my PR green", or "monitor CI checks".
File reference material into the filesystem (default ~/Documents/Reference). Use when routing non-actionable items to reference, cleaning up a filesystem inbox, or migrating reference material from another sync service.
Manage git worktrees for parallel development. Use when the user wants to work on multiple branches simultaneously, create isolated environments for features/fixes, or clean up completed worktrees.
After working on the code, ensure the branch contains only the minimal, idiomatic changes by removing AI-generated slop introduced on this branch.
This skill should be used when completing branches, merging to main, creating PRs with GitButler, or when `--complete-branch` flag is mentioned.
Narrative templates for git history documentation. Used by /git:code-story command.
Your bulletproof guide to executing implementation phases! Handles commits, detects when phases are too big, and knows when to bail cleanly. Load this whenever you're implementing a phase - it provides clean commit protocol and signals the orchestrator when things go sideways.
