Total 50,473 skills, Version Control has 883 skills
Showing 12 of 883 skills
Guide for recovering lost Git commits, resolving detached HEAD states, and fixing common Git repository issues. This skill should be used when users need help recovering from Git mistakes such as lost commits, detached HEAD situations, accidental resets, or when commits appear to be missing from branches.
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.
This skill should be used when the user asks to "finish a hotfix", "merge hotfix branch", "complete hotfix", "git flow hotfix finish", or wants to finalize a hotfix and merge it into main and develop.
Complete workflow for handling GitHub PR reviews using gh pr-review extension
Securely authenticate with GitHub using stored credentials for API operations and git commands
Validate the current Pull Request branch name, body, and status against Marshroom conventions
Commit changes, push to GitHub, and open a PR. Includes quality checks (security, patterns, simplification). Use --quick to skip checks.
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or runs /commit-staged or /commit-creator commands.
Intelligently detects when too many files are staged and automatically groups them by feature or functionality using Conventional Commits with user language preference
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
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.
Commit changes from the current Claude Code session to a new branch, push to GitHub, and open a PR. Use when the user wants to save their work as a PR, submit session changes, or create a pull request for what was done in this session.