Total 52,846 skills, Version Control has 913 skills
Showing 12 of 913 skills
Generate clear, conventional commit messages from staged changes. Use when the user asks to commit or needs a commit message.
Use when syncing all git repos under ~/code across machines, typically at end-of-day (push) or start-of-day (pull). Triggers on「同步代码」「code-sync」「下班同步」「上班更新」.
Create or update pull requests for the current branch
This skill should be used when the user asks to "create a pull request", "create PR", "open PR", "update a pull request", "update PR", "create an issue", "file an issue", "create a GitHub issue", "create a Claude Code issue", "report a bug in Claude Code", "create a Codex issue", "report a bug in Codex CLI", "create a Sablier issue", "file an issue in sablier-labs", "create a discussion", "start a GitHub discussion", or mentions OSS contribution workflows.
Summarizes git commits for specified users over a given time period and generates markdown reports
This skill should be used when you need to create, open, or edit a pull request (PR), or the user asks to "create a PR", "open a PR", "submit a PR", "raise a PR", "file a PR", "make a PR", "create a pull request", "open a pull request", "new PR", or any variation requesting GitHub pull request creation.
Bitbucket Git repository hosting with Pipelines. Use for Atlassian teams.
Create and manage multi-repo development workspaces for complex tasks involving multiple repositories, dependencies, and parallel agent work. Use when the user wants to set up a workspace, add repos/worktrees/deps to an existing workspace, or initialize a project that spans multiple repositories. Triggers on requests like "create a workspace", "set up a multi-repo project", "add a repo to the workspace", or "create a worktree".
Generate professional git commit messages following Conventional Commits specification. Use when user asks to commit changes or write a commit message.
Git workflow helper for conventional commits, confidence-scored code review, and pull request management. Use when: committing changes, reviewing code, creating PRs, generating PR descriptions, analyzing diffs. Triggers on "commit", "review", "push", "create PR", "PR description", "summarize changes".
Branch naming conventions, Git Flow vs trunk-based development, feature branch lifecycle, and release strategies. Reference when creating branches, planning releases, or choosing a branching model.
Commit unstaged changes, push changes, submit a pull request.