Total 44,141 skills, Version Control has 798 skills
Showing 12 of 798 skills
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.
Create GitHub pull requests. Use when user asks to "create a pull request", "open a PR", "/create-pr", or requests creating pull requests.
Create git commits following repository style. Use when user asks to "create a commit", "commit changes", "/commit", or requests committing code to git.
This skill provides guidance for recovering secrets or sensitive data that have been removed from Git history through operations like reset or rebase, and then properly cleaning up the repository to ensure the data is completely removed. Use this skill when tasks involve finding lost commits, recovering data from Git reflog, or securely removing sensitive information from Git repositories.
Perform git commit following Conventional Commits standards
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
Format commit messages following project conventions with commitlint validation. Use when committing changes, writing PR descriptions, or preparing releases.
Repository management strategies including branch strategies (Git Flow, GitHub Flow, trunk-based), monorepo patterns, submodules, and repository organization. Use when user needs guidance on repository structure or branching strategies.
Create branch, commit, push, and open a pull request. Use when: user says "ship it", "ship this", "create a PR", "open a PR", "push and PR", or wants to go from uncommitted changes to an open pull request.
Use when working on multiple branches simultaneously, context switching without stashing, reviewing PRs while developing, testing in isolation, or comparing implementations across branches - provides git worktree commands and workflow patterns for parallel development with multiple working directories.
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
Intelligently detects when too many files are staged and automatically groups them by feature or functionality using Conventional Commits with user language preference