Total 53,176 skills, Version Control has 921 skills
Showing 12 of 921 skills
GitLab label operations. ALWAYS use this skill when user wants to: (1) list project labels, (2) create new labels, (3) manage label colors and descriptions.
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' 키워드가 포함된 작업 시
Groups related git changes into coherent commits and drafts commit messages. Use when the user asks to commit, commit current changes, or create a commit.
Use when starting any RLM requirement to set up an isolated git worktree. REQUIRED before Phase 1 - creates isolated workspace, verifies clean test baseline, and prevents main branch pollution.
Create and submit Gitee pull requests with team convention enforcement. Use when the user asks to open/submit a Gitee PR on gitee.com and needs an automated flow that validates branch naming, commit prefixes, clean working tree, optional auto-commit, branch push, and PR creation.
Manage parallel development with cmux-style git worktrees in one repository. Use this skill whenever the user asks to run multiple agents in parallel, create or resume isolated worktrees, list/switch/merge/remove worktrees, set up `.cmux/setup`, or recover from worktree conflicts. In this environment, always use the `cmx` alias in commands.
Always apply this skill when committing to git
Create or configure a fork workflow with git-town. Preflight checks at every step. TRIGGERS - fork repo, setup fork, git-town fork, create fork, fork workflow, upstream setup.
Branch and PR workflow for Engram contributors. Trigger: When starting any change that will be proposed through GitHub.
The human project owner and final authority. Does not write code or run tools -- resolves tie-breaks, approves or denies major decisions, and unblocks deadlocks.
Stage 2 (REX mode only) — Git archaeology, changelog analysis, verified factual timeline. Skip automatically in Concept mode.
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.