Total 50,472 skills, Version Control has 883 skills
Showing 12 of 883 skills
Manage git-tracked directories correctly - never create .gitkeep files in directories that will immediately contain tracked files
Move files using a two-phase approach that preserves Git history. Phase 1 uses mv commands only, then waits for staging. Phase 2 makes content changes separately. Use when reorganizing files and need clean, trackable diffs. Triggers on "move files", "reorganize structure", "preserve git history".
Create and submit Gitee pull requests with team convention enforcement. Use when the user asks to open/submit a Gitee PR on gitee.com and needs an automated flow that validates branch naming, commit prefixes, clean working tree, optional auto-commit, branch push, and PR creation.
Git-aware smart revert for tracks, phases, and tasks. Handles rewritten history, finds related commits, and provides safe rollback with multiple confirmation gates.
Use when opening a pull request, submitting code for review, or when the user says "create PR," "open PR," or "/gh-pr-create." Generates conventional-commit title and structured body from branch commits.
Automates git commits with WBS tracking and code review. Use when user wants to commit changes or needs commit message suggestions. Keywords: commit, 커밋, 커밋해줘, 커밋 메시지, git commit, WBS, 리뷰
[Git] Resolve git merge/cherry-pick/rebase conflicts with backup, analysis, and reporting
(hal-9000) Use when editing any file under plugins/hal-voice/ to bump the plugin version before committing
Commit and push ALL changes (staged + unstaged + untracked) to the remote repository
Branch and PR workflow for Engram contributors. Trigger: When starting any change that will be proposed through GitHub.
Summarize code changes by author type and scope. Inputs are author and scope with product plus PR as defaults.
Generate Git branch names from staged or branch changes