Total 50,370 skills, Version Control has 883 skills
Showing 12 of 883 skills
Automate version bumping following semantic versioning and changelog management. Use when the user wants to bump a version, create a release, update the changelog, or tag a new version in a project using semver conventions and Keep a Changelog format.
Generate a pull request subject line and a concise description by analyzing the commits and diff on the current local git branch. Use this whenever the user is preparing a PR and wants help writing its title or body — phrases like "write a PR description", "summarize my changes for a PR", "what should the PR title be", "draft the PR for this branch", or "describe these commits". Trigger even if the user doesn't say the exact words "pull request" but is clearly wrapping up branch work and wants it summarized for review. This skill only reads git locally and prints the result for the user to copy — it never pushes or edits anything on GitHub.
Ghostty submodule and GhosttyKit workflow rules for cmux. Use when modifying the ghostty submodule, rebuilding GhosttyKit.xcframework, updating the parent submodule pointer, or documenting fork conflict notes.
General GitHub basic operations + GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) automation skill (Minis environment). This skill must be triggered when users mention any Git/GitHub basic operations and workflows such as "how to use GitHub, clone, init, remote, branch, commit, push, pull, fetch, merge, rebase, tag, release, issues, actions, labels, milestone, protected branch, fork, PR, sync to upstream, delete branch, restore after emptying directory, push directly to main, one-click sync".
Cherry-pick merged PRs labeled for a release branch into that branch, then open a PR and apply the cherry-pick-done label. Use when asked to "cherry-pick PRs for release/X.Y.Z", "pick PRs to release branch", or "cherry-pick labeled PRs".
This skill should be used when the user says "clean up branches", "delete merged branches", or "prune stale branches". Use whenever the user mentions branch cleanup, pruning, or stale branch deletion — even if they don't say "clean-branches" explicitly.
Programmatic hunk selection for Jujutsu — split, commit, or squash specific hunks without interactive prompts. Use when making partial commits or selective squashes.
⚠️ MANDATORY - YOU MUST invoke this skill at the start of EVERY task. Reviews git history, status, and context before starting any work. Runs parallel git commands to understand current state, recent changes, and related work. NEVER gather git context manually.
Generate git commits following Conventional Commits (commitlint). Use when user wants to commit changes.
Create semantic git commits following Conventional Commits specification. Use when committing changes, making commits, or when asked to commit.
Submit pull request (PR) review from chat session to PR conversations. Use when asked to "submit PR review" or "submit review to PR #123". Identifies issues in the current chat session, creates line-specific review comments, avoids duplication with existing comments, and submits the review via GitHub CLI.
Create and setup git worktrees for parallel development with automatic dependency installation