Total 43,988 skills, Version Control has 795 skills
Showing 12 of 795 skills
Create high-quality Pull Requests with conventional commits and proper descriptions. Trigger: When creating PRs, writing PR descriptions, or using gh CLI for pull requests.
Create a git commit following the Conventional Commits specification.
Comprehensive review of staged Git changes for risk assessment, error detection, and impact analysis. Use when the user wants to review staged changes, check for errors before commit, analyze risks in git staged files, validate code changes before committing, or needs suggestions on staged modifications.
Advanced Git operations automation including intelligent branching, commit optimization, release workflows, and repository health management
Standardized git commits following Conventional Commits. Supports mapping to GitHub and GitLab.
Narrative templates for git history documentation. Used by /git:code-story command.
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.
Isolated workspace creation - creates git worktrees with smart directory selection and safety verification for parallel feature development.
Branch completion workflow - guides merge/PR/cleanup decisions after implementation is verified complete.
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