Total 50,476 skills, Version Control has 883 skills
Showing 12 of 883 skills
Help address review/issue comments on the open GitLab MR for the current branch using glab CLI. Use when the user wants help addressing review/issue comments on an open GitLab MR
Stage changes and generate commit messages that comply with the Conventional Commits specification.
Commits with perfect messages. Use when making a commit.
Draft and validate commit messages that comply with Conventional Commits 1.0.0. Use when writing git commit messages, enforcing commit format in reviews/CI, mapping commits to SemVer intent, or converting plain-language change notes into spec-compliant messages with optional scope, body, footers, and breaking-change markers.
Prepare a GitHub PR for merge by rebasing onto main, fixing review findings, running gates, committing fixes, and pushing to the PR head branch. Use after /review-pr. Never merge or push to main.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Create git commit messages based on current staged changes. Has support for git emoji messages.
Git-centric implementation workflow. Enforces clean checkout, creates a properly named branch, tracks progress in a WIP markdown file, and commits continuously so git logs serve as the primary monitoring channel. Use when starting instructed, offer for any plan-based implementation task.
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.
Create standardized git commit messages. Prioritize following the project's existing commit conventions, and support the Conventional Commits format. Usage scenarios: Users request to create commits or write commit messages
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
Write detailed Conventional Commit messages using only the active chat conversation as context. Use when the user asks for commit messages based on discussion history, requests module-scoped commit subjects, or explicitly forbids checking git logs, diffs, or code files.