Total 30,488 skills, Version Control has 598 skills
Showing 12 of 598 skills
Enforces using git stash before file deletion and prohibits direct rm/unlink commands. Use when deleting files, cleaning up codebase, or removing tracked/untracked files. MUST ALWAYS be applied when file deletion is needed.
Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.
Manage git-tracked directories correctly - never create .gitkeep files in directories that will immediately contain tracked files
Analyzes changes since last release and updates CHANGELOG.md ONLY. Does NOT trigger releases.
Create pull requests on GitHub using GitHub MCP, GitHub CLI (gh), or the GitHub REST API. Use this skill when the user wants to submit changes as a pull request, following repository standards and templates.
Create and execute Git commits in Conventional Commits format with a required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.
Automate versioning and changelog generation using semantic versioning principles. Configure release automation, version bumping, and changelog tools. Use when implementing version management or automating release processes.
Creates context-aware git commits with smart pre-commit checks, submodule support, and conventional commit message generation. Use when user requests to commit changes, stage and commit, check in code, save work, save changes, push my code, finalize changes, add to git, create commits, run /commit command, or mentions "git commit", "commit message", "conventional commits", "stage files", "git add", or needs help with commits.
Git operations guide. Provides how-to for common git tasks. Use when: - Writing commit messages (Conventional Commits format) - Understanding git workflows
Manage git worktrees for efficient multi-branch development. Use when you need to create worktrees for feature branches, organize worktree directories, clean up unused worktrees, or implement worktree-based workflows.
Create Git commit messages that conform to Conventional Commits 1.0.0, including type/scope/description format, optional body, trailer-style footers, and explicit BREAKING CHANGE signaling. Use when users ask to draft commit messages, commit current changes, rewrite a commit message into conventional format, or enforce conventional commit standards in a repo.
Work with GitHub in this repo: PR creation, CI checks, and gh CLI operations.