Total 50,474 skills, Version Control has 883 skills
Showing 12 of 883 skills
Use when starting a new feature branch, creating isolated development environments, or working on multiple tasks simultaneously without stashing or switching branches. Triggers: user says "worktree", "new branch for work", "parallel development", "isolated environment", needs to work on two things at once.
Create well-formatted conventional commits in a repository hosted on Azure DevOps (ADO / Azure Repos). Use this whenever the user asks to commit changes and the project is on Azure DevOps — dev.azure.com, visualstudio.com, or explicit mentions of ADO, Azure Repos, or work item IDs like `AB#1234`. Automatically appends `AB#<id>` work-item trailers when the branch name or staged changes reference one, and attributes AI-assisted authorship.
Analyzes git commits and changes within a timeframe or commit range, providing structured summaries for code review, retrospectives, work logs, or session documentation.
Merge all worktrees from .trees/ into current branch and clean up
Branch finishing and PR preparation. Use when completing a feature branch, preparing a pull request, or cleaning up commit history.
Git worktree lifecycle management. Use when creating, navigating, syncing, or cleaning up git worktrees for parallel development.
Fork a GitHub repo and clone it locally with proper remote setup
Use this skill when the user asks to create a PR, open a pull request, "create-pr", "submit a pull request", or "open a merge request". Requires Gitee MCP Server to be configured.
This skill should be used when executing the epic-dev workflow, creating epic branches, managing sprint phases, working with git worktrees for phased feature development, or when the user mentions "epic workflow", "sprint phases", "phased development", or "git worktree workflow".
[Hyper] Push unpushed commits to the remote. Discovers the current or descendant git repositories, checks for commits ahead of upstream, and pushes them. Use when the user wants to push, sync to remote, or send commits upstream.
[Hyper] Create one or more Conventional Commits from the current repository state. Inspect staged and unstaged changes, group them into logical change sets, generate a compliant message per group, and commit each group separately in sequence.
Create git commits in Conventional Commits format. Estimate type/scope from staged changes, detect breaking changes and secret leaks (such as .env files). Must pass pre-commit hooks (`--no-verify` is not allowed). Use with instructions like "commit", "git commit", "record changes".