Total 43,555 skills, Version Control has 792 skills
Showing 12 of 792 skills
[Git & Release] Update CHANGELOG.md [Unreleased] section with business-focused entries via systematic file review
Use when creating temporary files, drafts, experiments, or any content that should not be committed to version control. Ensures proper placement in .claude/.scratch with gitignore configuration.
This skill should be used when the user asks to "commit", "make a commit", "commit my changes", "create commits", "git commit", or wants to commit staged/unstaged changes with logical grouping and conventional commit format.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Create git commit messages based on current staged changes. Has support for git emoji messages.
Create a Pull Request from the current branch. Syncs upstream main/master, updates current branch, handles fork remotes intelligently, and generates PR title/description from diff and commits. Respects PR templates if present. REQUIRES Must be in a git repository with gh CLI available.
Git 2.49+ features including git-backfill, path-walk API, and performance improvements
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or runs /create-pr or /pr-creator commands.
Sync a commit from the gemini remote into sync-upstream for empower-site.
Commit staged changes with appropriate commit messages
Push branch and create GitHub pull request (auto-assigned)
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.