Total 30,670 skills, Version Control has 603 skills
Showing 12 of 603 skills
Manages version control with Jujutsu (jj), including rebasing, conflict resolution, and Git interop. Use when tracking changes, navigating history, squashing/splitting commits, or pushing to Git remotes.
Generate concise, descriptive git commit messages following best practices. Use when creating git commits from staged changes, crafting commit messages, or reviewing commit message quality. Use when the user says /commit or asks to create a git commit.
Creates GitHub pull requests with properly formatted titles. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request. Analyzes changes on the current branch and uses the pull request template from .github folder.
Automated changelog generation with semantic versioning. Triggers on: generating changelogs, updating versions, releasing software, version bumps, changelog updates, semantic versioning, and when users ask to "update changelog", "bump version", "create release", or "generate changelog". Use when user: needs to update CHANGELOG.md, bump package.json version, create a release, generate changelog entries, or follow semantic versioning and Keep a Changelog standards.
Open a draft pull request on GitHub. MUST use when you want to create/open a PR.
Git worktree management with safe defaults and flexible placement strategies. Use when users ask to: (1) create a new worktree or work on multiple branches in parallel, (2) list existing worktrees, (3) remove or clean up worktrees, (4) manage worktree placement (subfolder vs sibling directory), or any other git worktree operations.
Create atomic conventional git commit and push to remote repository. Use when committing staged changes with conventional commit format and immediately pushing to the remote branch.
Resolve GitHub issues using isolated worktrees and TDD
This skill should be used when the user asks to "finish a release", "merge release branch", "complete release", "git flow release finish", or wants to finalize a release and merge it into main and develop with a tag.
This skill should be used when the user requests "commit", "git commit", "create commit", or wants to commit staged/unstaged changes following conventional commits format
This skill should be used when the user asks to "finish a feature", "merge feature branch", "complete feature", "git flow feature finish", or wants to finalize and merge a feature branch into develop.
Generate high-quality git commit messages following Conventional Commits and Chris Beams' Seven Rules. Infers WHY from context and provides clear guidance on structure, scope, and body content.