Total 53,505 skills, Version Control has 923 skills
Showing 12 of 923 skills
Analyze and address unresolved feedback on a GitHub pull request. Use when the user has received PR review comments and wants to systematically address each piece of feedback, or when the user mentions PR feedback, review comments, or addressing reviewer concerns.
Essential Git patterns for effective version control, eliminating redundant Git guidance per agent.
Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
Use when updating GitHub PR title or body. Works around the gh pr edit GraphQL bug caused by GitHub's Projects Classic deprecation.
Create Pull Requests following best conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review.
Generate conventional git commit messages following Angular convention format. Use this skill when creating commits, writing commit messages, or reviewing git history. Triggers include "git commit", "commit message", "changelog", or requests to version control changes.
Complete workflow for handling GitHub PR reviews using gh pr-review extension
This skill should be used when the user asks to "finish a release", "merge release branch", "complete release", "git flow release finish", or wants to finalize a release and merge it into main and develop with a tag.
Use Git worktrees for isolated work environments. Creates separate working directories for parallel development on different branches.
Create atomic conventional git commit and push to remote repository. Use when committing staged changes with conventional commit format and immediately pushing to the remote branch.
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
Pre-release preparation. Reset version numbers, update CHANGELOG and README, verify consistency.