Total 50,370 skills, Version Control has 883 skills
Showing 12 of 883 skills
Writing pull request titles and descriptions for the tldraw repository. Use when creating a new PR, updating an existing PR's title or body, or when the /pr command needs PR content guidance.
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
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.
Create standardized git commits using Conventional Commits with Gitmoji. Use when the user asks to commit changes, create a commit, or says "/commit". Analyzes staged/unstaged diffs and generates semantic commit messages with emoji prefixes.
Git workflow and conventions — branching, commit messages, and PR creation.
Work with Graphite (gt) for stacked PRs - creating, navigating, and managing PR stacks.
Use this when you need to start feature development isolated from the current workspace, or before executing implementation plans — ensure an isolated workspace exists via native tools or the git worktree fallback mechanism
Prepare local GitHub issue branches from the repository default branch using GitHub-style issue branch names. Use when starting issue-linked work, when the user says new branch for an issue, or when an agent must move onto the correct issue branch before implementation.
Perform common Git operations safely with sandbox-aware failure handling. Use whenever the user wants to inspect or modify git state, especially for cherry-pick, merge, rebase, commit, branch, stash, or worktree workflows. Always use this skill when the user mentions a Git failure, conflict, cherry-pick, merge issue, worktree, branch checkout problem, lock file, permission denied, operation not permitted, or any case where a sandboxed agent might confuse an environment restriction with a real code conflict. Be proactive: if the task smells like Git state or Git write behavior, use this skill even if the user did not explicitly ask for a 'Git' workflow.
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
Create well-formatted commits with conventional commit format.