Total 50,395 skills, Version Control has 883 skills
Showing 12 of 883 skills
Carefully integrate one Git branch into another without blindly accepting a mechanical merge or losing source-branch intent. Use when manually merging, transplanting, or refactoring branch work; when the user says not to blindly merge; when resolving conflicts while preserving clean current-branch structure; or when auditing that source additions, removals, tests, and docs all landed intentionally.
This skill should be used when the user says "get PR comments", "show PR feedback", "what comments on my PR", "PR review comments", "show me the review", "what did reviewers say", or asks about feedback on a pull request. Not for creating PRs or responding to comments.
This skill should be used when the user says "commit my changes", "commit this", "create a commit", "git commit", "save my work", or mentions committing code.
This skill should be used when the user wants to create a pull request, or submit code for review. Triggers on "push a PR", "create a PR", "open a pull request", "make a PR", "submit for review".
Manage version control with Jujutsu (jj) — no staging area, immediate changes, smart rebasing. Use when navigating history, squashing, or pushing to Git remotes.
Use git-gud (gg) to manage stacked diffs with GitHub PRs or GitLab MRs. Use this when creating stacks, syncing updates, checking CI/review state, and landing approved work safely.
GitHub PR lifecycle: branch, commit, open, CI, merge.
Write, edit, review, or improve concise issue, pull request, and merge request titles, bodies, and comments for GitHub, GitLab, and similar platforms.
Git workflow guidance for commits, branches, and pull requests
This skill should be used when the user wants to bump versions, create releases, or tag versions. Triggers include: "bump version", "bump the version", "version bump", "release version", "tag a release", "create release", "major/minor/patch bump", "update version", "new version", "/version". Updates plugin.json and marketplace.json. Creates git tag and commit.
This skill should be used when the user asks to "start a hotfix", "create hotfix branch", "fix a critical bug", "git flow hotfix start", or wants to begin a hotfix for a production issue.
Create a git commit with conventional commit format. MUST use anytime you want to commit changes.