Total 30,617 skills, Version Control has 603 skills
Showing 12 of 603 skills
Commit changes from the current Claude Code session to a new branch, push to GitHub, and open a PR. Use when the user wants to save their work as a PR, submit session changes, or create a pull request for what was done in this session.
Blocks destructive git and filesystem commands before execution. Prevents accidental loss of uncommitted work from git checkout --, git reset --hard, rm -rf, and similar destructive operations. Works as a Claude Code PreToolUse hook with fail-open semantics.
Generate Chinese Git commit messages that comply with the Conventional Commits specification. Use this when users request to create Git commits, generate commit messages, or mention "submit code", "git commit", or "Chinese commit". Automatically analyze code changes to generate standardized Chinese commit messages with correct type prefixes (feat/fix/docs, etc.) and clear descriptions.
Perform git commit following Conventional Commits standards
Creates commits with conventional format and validation. Use when committing changes or generating commit messages.
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing commits.
Use the Forgejo CLI (fj) to authenticate and operate on a Forgejo instance (issues, PRs, repositories) with correct host handling.
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments, creating isolated SPEC workspaces, managing git worktrees, or working on multiple features simultaneously. Do NOT use for regular git operations like commit or merge (use manager-git agent instead).
This skill should be used when the user: - Wants to work on multiple branches simultaneously or in parallel - Needs to start a new feature/task while preserving current work - Asks about git worktree operations (create, remove, list, clean) - Mentions "twig" commands (add, remove, clean, list, init) - Wants to carry or move uncommitted changes to a new branch - Wants to copy/sync changes between branches - Needs to isolate work in a separate directory - Asks about switching context without stashing - Wants to clean up old/merged branches and their worktrees - Says phrases like "new worktree", "create worktree", "branch off", "work on something else", "start new work", "parallel work", "separate workspace", "another branch" Use this skill for ANY worktree-related operation, not just when explicitly asking about twig.
This skill provides guidance for recovering secrets or sensitive data that have been removed from Git history through operations like reset or rebase, and then properly cleaning up the repository to ensure the data is completely removed. Use this skill when tasks involve finding lost commits, recovering data from Git reflog, or securely removing sensitive information from Git repositories.
Create git commits following repository style. Use when user asks to "create a commit", "commit changes", "/commit", or requests committing code to git.