Total 43,520 skills, Version Control has 790 skills
Showing 12 of 790 skills
**REQUIRED** - ALways activate FIRST on any git/VCS operations (commit, status, branch, push, etc.), especially when HEAD is detached. If `.jj/` exists -> this is a Jujutsu (jj) repo - git commands will corrupt data. Essential git safety instructions inside. DO NOT IGNORE.
Generate git commit messages and help with git workflows
Creates changesets for semantic versioning and automates release notes. Determines correct version bump type (patch/minor/major) and generates well-documented changelog entries. Triggers on: add changeset, create changeset, version bump, prepare release, CHANGELOG, breaking change, pnpm changeset.
Generates changelogs and manages releases. Use when updating changelogs, pushing changelog changes, preparing releases, or tagging versions.
Generate and manage changelogs from git history. Use for release notes, tracking breaking changes, and maintaining project history.
Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.
Help backport PRs to release branches using the backport CLI tool. Use when backporting changes that have merge conflicts requiring manual resolution.
[Git & Release] Stage, commit and push all code in the current branch
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
PR stacking workflow for breaking large features into smaller, dependent PRs. Use when planning multi-step features, creating dependent branches, or rebasing stacked changes.
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Generate well-formatted git commit messages following conventional commit standards