Total 43,576 skills, Version Control has 792 skills
Showing 12 of 792 skills
A comprehensive Git command assistant and workflow guide. Trigger whenever the user asks how to perform a specific Git operation, wants to know what a Git command does, needs help fixing a Git mistake, or wants guidance on Git best practices (like branching, rebasing, or squashing).
合并 - Complete PR lifecycle: worktree → implement → commits → PR → verify → merge. 触发条件/Triggers: 需要实现功能并提交 PR、修复 Issue、或完成代码审查后的合并工作。 工作流/Workflow: - 阶段 0/Phase 0: 创建工作树/Create worktree - 阶段 1/Phase 1: 实现功能/Implement feature - 阶段 2/Phase 2: 创建 PR/Create PR - 阶段 3/Phase 3: 验证循环/Verification loop (CI + Review + Approval) - 阶段 4/Phase 4: 合并清理/Merge & cleanup 命令/Commands: - /合并 <任务> - 启动完整 PR 工作流 - /合并 create <任务> - 创建 PR - /合并 check - 检查验证状态 - /合并 status - 查看 PR 状态 - /pr <task> - English command 能力/Capabilities: 工作树管理、功能实现、原子提交、PR 创建、验证循环、合并清理。
Automatically stage, commit and push with Git. Use this skill when the user requests to commit code, push code, commit, push, commit and push, auto commit, stage commit push, or any operations involving git commit/push. It is also applicable to colloquial expressions from users such as "submit it", "push the code", "help me commit", "push it up", "only commit", "just commit", etc.
Run a Cyrus release by publishing all packages to npm in the correct dependency order, updating changelogs, and creating git tags.
Manage parallel development with Git worktrees. Covers worktree creation with port allocation, environment sync, branch isolation for multi-agent workflows, cleanup automation, and Docker Compose integration. Use when working on multiple branches simultaneously, running parallel CI validations, or isolating agent workspaces.
This is used to review comments on an active pull request and decide whether to accept, iterate, or reject the changes suggested in each comment.
Use when starting new feature work to create isolated git worktrees with smart directory selection and safety verification. Keeps main branch clean while developing.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guide the conclusion of development work by providing structured options such as merging, PR, or cleanup
Use this before starting feature development isolated from the current workspace or executing implementation plans — create isolated git worktrees with intelligent directory selection and security validation
Create a pull request with Conventional Commits formatting, a templated body, and local verification. Use when the user asks to create a PR, open a PR, submit changes for review, or put code up for review.
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.
Generate ultra-compact commit messages. Follows the Conventional Commits format with subject ≤50 characters, prioritizing "why" over "what". Supports both Japanese and English. Trigger with "Make a commit message", "/commit", or "/genshijin-commit". Auto-trigger candidate when staging changes.