Total 43,459 skills, Version Control has 790 skills
Showing 12 of 790 skills
Use when the user wants to commit changes. Stages files, updates CHANGELOG.md, and creates a commit following project conventions.
Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
Analyzes git diff and commit history to write PR title and description based on the project's PR template.
Create GitHub pull requests with readiness checks, auto-drafted titles and descriptions, and remote push handling. Use when: create PR, pull request, open PR, submit PR, create pull request, PR for review, push and PR, pull-request, /pull-request.
This skill should be used when the user asks to "implement a feature in an isolated worktree", "create a worktree from the current project branch", "open a PR from worktree changes", "merge feature PRs into main", "run multiple agents in parallel worktrees", or "handle worktree merge conflicts and incompatibilities".
GitHub CLI(gh)를 활용한 GitHub 플랫폼 상호작용 가이드. 다음 상황에서 사용: (1) GitHub 이슈 생성, 조회, 수정 시, (2) Pull Request 생성, 리뷰, 병합 시, (3) GitHub 릴리스 생성 및 관리 시, (4) 레이블, 마일스톤 등 프로젝트 관리 시, (5) GitHub Actions 워크플로우 실행 및 결과 조회 시, (6) 'gh', 'issue', 'pull request', 'PR', 'release', 'label', 'workflow', 'run' 키워드가 포함된 작업 시
Get up to speed on the current branch's intent by analyzing commits, changes, and optionally a Linear ticket. Use when starting work on an existing branch.
Produces a gh CLI command to create a draft PR using the repo's PR template, filling the body from the current branch's commits and conversation context. Use when the user asks for a draft PR, create draft PR, open a PR with gh, or wants a PR command following the template.
Analyzes git diffs and commit history to intelligently fill PR templates and create pull requests via gh CLI. Use when user wants to create a PR, needs PR description help, or says 'create a pull request', 'fill PR template', 'make a PR', 'open a pull request', or mentions PR creation.
Create feature branches linked to issues with consistent naming conventions. Generates branch names from issue numbers and descriptions, creates the branch, and checks it out. Use when: create branch, new branch, feature branch, branch for issue, start working on issue, branch-create, /branch-create.
Resolve PR review comments
Move files using a two-phase approach that preserves Git history. Phase 1 uses mv commands only, then waits for staging. Phase 2 makes content changes separately. Use when reorganizing files and need clean, trackable diffs. Triggers on "move files", "reorganize structure", "preserve git history".