Total 50,505 skills, Version Control has 883 skills
Showing 12 of 883 skills
Generates properly formatted Git branch names following project conventions. Use this skill whenever the user wants to name a branch, create a branch, or asks things like "what should I call this branch?", "what branch name should I use?", "help me with the branch name", or describes a feature/fix and needs a branch name. Always use this skill when the user needs a git branch name, even if they don't explicitly say "branch".
GitHub operations expert for PRs, issues, code review, Actions, and gh CLI
Jujutsu (jj) version control, load skill when hook output shows vcs=jj-colocated or vcs=jj in the system-reminder.
Commit and push in one step. Use when user says "/cp", "commit and push", "커밋하고 푸시", "커밋 푸시", or wants to stage, commit, and push changes in a single action. Optionally accepts a commit message as argument.
Interact with GitHub repositories, pull requests, issues, and workflows using the GITHUB_TOKEN environment variable and GitHub CLI. Use when working with code hosted on GitHub or managing GitHub resources.
Stage all changes, create commit, and push to remote. Use when asked to "push everything", "commit and push all", "push all my changes", or for bulk operations. Includes safety checks for secrets, API keys, and large files. Requires explicit user confirmation before executing. Use with caution.
Semantic versioning guidelines for software releases. Use when assigning version numbers, deciding between major/minor/patch bumps, managing unstable (0.x.x) software versions, evaluating breaking changes, or reviewing changelogs and release notes for correct semver compliance.
Extract and respond to comments from a GitHub Pull Request. Use this skill when given a GitHub PR URL to review comments and act on the feedback, or when asked to address PR review feedback.
Creates or updates a GitHub pull request for the current branch. Use when ready to submit code changes for review.
Essential Git patterns for effective version control, eliminating redundant Git guidance per agent.
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.
lazygit terminal UI for git. Use for git operations.