Total 44,044 skills, Version Control has 796 skills
Showing 12 of 796 skills
Summarize current work, commit, push, and create or update a PR. Automatically write conversation context into the PR description to ensure reviewers can quickly understand the background.
Finalize development branches for integration. Prepares branches for merging with cleanup, rebasing, and verification steps.
Resolve merge conflicts systematically with context-aware 3-tier classification and escalation protocol
Generate concise PR descriptions by analyzing the diff against a base branch
Build high-signal PR context for review with diff analysis, risk assessment, and discussion questions
Git branching strategy expertise with flow-aware automation. Auto-invokes when branching strategies (gitflow, github flow, trunk-based), branch creation, branch naming, merging workflows, release branches, hotfixes, environment branches, or worktrees are mentioned. Integrates with existing commit, issue, and PR workflows.
Modern Git command best practices for AI agents. Use modern, purposeful commands introduced in Git 2.23+ instead of legacy multi-purpose commands. Teaches when to use `git switch` (branch operations), `git restore` (file operations), and other safer alternatives to improve clarity and reduce errors.
Create, review, and safely update `.gitattributes` files with conservative Unix-first defaults and explicit attribute rationale.
Interactive git and GitHub tutor that teaches through hands-on practice in VS Code's terminal. Adapts to any skill level — from someone who's never opened a terminal to principal engineers filling knowledge gaps. Covers git commands, concepts, branching, merging, rebasing, GitHub workflows, and more. Tracks progress, streaks, and achievements in a `.git-tutor/` folder. USE THIS SKILL whenever the user wants to learn git, practice git, understand git concepts, get a git tutorial, learn GitHub, or says things like "teach me git", "I want to practice git", "help me understand branching", "git tutorial", "I'm new to git", "how does git work", "let's do more git practice", or asks to start the git tutorial. Also triggers for questions about git concepts when the user seems to be in a learning context rather than needing a quick answer for active development work.
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
Git troubleshooting techniques including recovering lost commits, fixing merge conflicts, resolving detached HEAD, and diagnosing repository issues. Use when user encounters git errors or needs to recover from mistakes.
Advanced git operations including complex rebase strategies, interactive staging, commit surgery, and history manipulation. Use when user needs to perform complex git operations like rewriting history or advanced merging.