Total 52,261 skills, Version Control has 908 skills
Showing 12 of 908 skills
Use when the user asks to commit changes, organize commits, write commit messages, or split working-tree changes into Conventional Commits. Trigger on phrases like "commit my changes", "커밋해줘", "커밋 분리", "make commits", "/conventional-commit", or whenever the user wants to turn current changes into Conventional Commit-style commits. For commit + push use `conventional-commit-push`; for rewriting non-Conventional commit history use `conventional-commit-rewrite`.
Create a new worktrunk worktree and switch this session's working directory into it. Use when launching a session that should work in its own worktree (e.g. `/wt-switch-create my-branch <task>`), or mid-session to move work into a fresh branch.
Used in Git development when you need to abandon current attempts and roll back to a historical commit. It automatically archives the current state to the archive/ branch and establishes bidirectional links (source and target) in ARCHIVE.md to ensure traceability of the development decision flow. Suitable for scenarios requiring safe rollback while retaining the context of failed attempts.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Commit Changes
Update the title and body of one or more pull requests.
Turn the working tree into logical, atomic Conventional Commits — classify uncommitted files as in-scope vs out-of-scope against the branch's merge base, show a staging plan, and create one commit per coherent unit (type + optional scope + British-English body; `!` / `BREAKING CHANGE:` for breaking changes). Never `git add -A`; files that look like they belong to another branch/worktree are never staged silently. Use when asked to commit uncommitted work, tidy WIP into atomic commits, or as the commit step inside a ship flow (e.g. `/send-it`). It commits only — no push, PR, changelog, or Linear writeback.
Use when merging multiple reviewed PRs into one release branch on remote compute.
[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requirements, and AI-assisted development rules. Trigger: any task involving git commit, git push, PR creation, or code review.
合并 - Complete PR lifecycle: worktree → implement → commits → PR → verify → merge. 触发条件/Triggers: 需要实现功能并提交 PR、修复 Issue、或完成代码审查后的合并工作。 工作流/Workflow: - 阶段 0/Phase 0: 创建工作树/Create worktree - 阶段 1/Phase 1: 实现功能/Implement feature - 阶段 2/Phase 2: 创建 PR/Create PR - 阶段 3/Phase 3: 验证循环/Verification loop (CI + Review + Approval) - 阶段 4/Phase 4: 合并清理/Merge & cleanup 命令/Commands: - /合并 <任务> - 启动完整 PR 工作流 - /合并 create <任务> - 创建 PR - /合并 check - 检查验证状态 - /合并 status - 查看 PR 状态 - /pr <task> - English command 能力/Capabilities: 工作树管理、功能实现、原子提交、PR 创建、验证循环、合并清理。
Create a high-quality pull request: branch, focused changes, lint/build, conventional commit, and a clear PR description with validation steps. Use when the user asks to open or prepare a PR.
Fix GitHub issues end-to-end — from analysis through branch creation, implementation, testing, and PR submission. Use this skill whenever the user mentions fixing a GitHub issue, resolving a bug from an issue tracker, working on a GitHub issue number, or says things like "fix issue