Total 30,584 skills, Version Control has 602 skills
Showing 12 of 602 skills
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.
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.
Git best practices, branching strategies, commit conventions, and PR workflows. Use when reviewing git history, writing commits, setting up branching strategy, or improving git practices. Triggers on "git best practices", "commit message", "branching strategy", or "PR workflow".
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
Use when establishing branching strategies, implementing Conventional Commits, creating or reviewing PRs, resolving PR review comments, merging PRs (including CI verification, auto-merge queues, and post-merge cleanup), managing PR review threads, merging PRs with signed commits, handling merge conflicts, or integrating Git with CI/CD.
Automate versioning with Node.js semantic-release v25+. TRIGGERS - npm run release, version bump, changelog, conventional commits, release automation.
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination
Create git commits following the Conventional Commits v1.0.0 specification (conventionalcommits.org). Use when the user asks to commit changes, says "/conventional-commit", or wants a well-structured commit message. Triggers on requests like "commit this", "commit my changes", "create a commit", or any git commit workflow. Analyzes staged/unstaged changes and produces compliant commit messages with proper type, scope, description, body, and footers.
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
Stage all changes, generate a descriptive commit message from the diff, commit, and push to the current branch's upstream.