Total 43,513 skills, Version Control has 790 skills
Showing 12 of 790 skills
[Git & Release] Stage, commit and push all code in the current branch
Unified git workflow for branch-first development: status/diff review, security-first commits, worktrees, and PR creation/review via gh. Auto-activates on: "commit", "push", "branch", "worktree", "pr", "pull request", "merge", "rebase", "git".
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.
Generates changelogs and manages releases. Use when updating changelogs, pushing changelog changes, preparing releases, or tagging versions.
Generate and manage changelogs from git history. Use for release notes, tracking breaking changes, and maintaining project history.
Configure GitHub authentication for Cyrus — gh CLI login and git config for creating pull requests.
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
Configure GitLab authentication for Cyrus — glab CLI login and git config for creating merge requests.
Create GitHub pull requests from the current branch with auto-generated titles, descriptions, reviewers, and labels. Use this skill whenever the user wants to create a PR, open a pull request, submit code for review, push changes for merge, or mentions "PR", "pull request", "code review", or "merge request". Also trigger when the user says things like "I'm done with this feature", "ready to submit", "open a draft PR", or "send this for review". Works with GitHub CLI by default, with guidance for GitLab and Bitbucket.
Review a PR and submit suggestions as comments, along with an optional approval/request for changes.