Total 53,448 skills, Version Control has 922 skills
Showing 12 of 922 skills
Follow up on an existing PR by rebasing on the base branch, addressing reviewer comments, fixing CI issues, and pushing updates. Use when the user provides a PR URL or number and wants to get it ready for merge.
Post-merge workflow resolution. Verifies PR merge status, backfills synthesis metadata, force-resolves review statuses, transitions to completed, and cleans up worktrees/branches. Use when the user says 'cleanup', 'resolve workflow', 'mark as done', or runs /cleanup. Do NOT use before PRs are merged.
Prepare local GitHub issue branches from the repository default branch using GitHub-style issue branch names. Use when starting issue-linked work, when the user says new branch for an issue, or when an agent must move onto the correct issue branch before implementation.
Reference for Domestic Git Platform Configuration - Differences in SSH/HTTPS/Credentials/CI Integration and Mirror Sync Configuration for Gitee, Coding.net, Jihu GitLab, and CNB. Only invoke when the user explicitly uses /chinese-git-workflow; do not trigger automatically based on context.
Generate high-quality Conventional Commit messages for repositories using conventional-changelog-conventionalcommits.
Create a pull request following project conventions
Manage Azure Repos including branches, pull requests, and code reviews. Use when working with Azure Repos or managing repository operations.
Complete workflow for handling GitHub PR reviews using gh pr-review extension
Analyzes git diff and commit history to write PR title and description based on the project's PR template.
Analyze git commits within a specified time range and generate a work retrospective report. Trigger words: retrospective, review commits, git review, what did I do today, work summary, daily review, retrospective
Creates or updates a GitHub pull request for the current branch. Use when ready to submit code changes for review.
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.