Total 50,395 skills, Version Control has 883 skills
Showing 12 of 883 skills
Convert noisy GitHub repository search results into recommendation-grade candidate lists with explicit metadata, freshness, traction signal, provenance labels, and rollback-safe reporting for maintenance PR workflows.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Analyze an in-progress git branch, compare it with the current master/main using a subagent, derive practical lessons, and generate a concise redo handoff. Use when restarting a messy branch, redoing work cleanly, extracting lessons from current changes, or preparing another agent to verify the handoff, align with the user, and rebuild from the default branch.
Create GitHub pull requests that follow the NemoClaw PR template. Use when the user wants to create a new PR, submit code for review, open a pull request, or push changes for review. Trigger keywords - create PR, pull request, new PR, submit for review, open PR, push for review.
Open a pull request for the current feature
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
Work with Git repositories from the command line.
Create an appropriate git commit from the working tree and session history. Default commit messages are in Japanese unless the repo says otherwise (e.g. AGENTS.md).
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
Create and push a signed git release tag. Use this skill when the user says "tag a release", "new release", "cut a release", "bump version", "release tag", "tag version", "push a tag", or any variation of wanting to create a new version tag. Also use when the user types "/release-tag" or "/release".
Use when the user needs help with conventional commits, semantic versioning, changelog generation, or commit message quality improvement. Triggers: user says "commit", "version bump", "changelog", "commit message", staging changes for commit, preparing a release.
Update the pull request body for the current branch in the current repository.