Total 30,617 skills, Version Control has 603 skills
Showing 12 of 603 skills
Split git changes into context-based micro-commits
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
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.
Push branch and create GitHub pull request (auto-assigned)
Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.
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.
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 git commits using conventional commits with scopes. Use when the user asks to commit, make a commit, save changes, or any git commit operation. Never include Co-Authored-By lines, AI agent mentions, or any reference to Claude, AI, or automated tooling in commit messages.
Use when creating "changelog", "release notes", "version updates", generating "CHANGELOG.md", or asking about "git history to changelog", "commit summary", "what changed since last release"
Essential Git commands and workflows for version control, branching, and collaboration.
Format commit messages following project conventions with commitlint validation. Use when committing changes, writing PR descriptions, or preparing releases.
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary