Loading...
Loading...
Found 348 Skills
Intelligently analyze code changes and split them into multiple logical commits based on functionality and change types. This skill should be used when users want to commit code changes, especially when there are multiple unrelated changes in the working directory.
Game development tools, asset pipelines, version control, build systems, and team development workflows for efficient production.
This skill should be used when the user asks to "commit changes", "craft a commit message", "stage and commit", "commit only session edits", or run a commit workflow with flags like --all, --deep, or --push. Creates atomic git commits with heuristic analysis, conventional-commit formatting, staging rules, optional deep analysis, and optional push.
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Advanced git rebase patterns for linear history, stacked PRs, and clean commit management. Use when rebasing branches, cleaning up commit history, managing PR stacks, or converting merge-heavy branches to linear history. Covers --reapply-cherry-picks, --update-refs, --onto, and interactive rebase workflows.
Remove AI-style noise from staged and branch diffs while preserving behavior and repository style.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - Guides the completion of development work by providing packaged options for merging, PR, or cleanup
Generate professional git commit messages following Conventional Commits specification. Use when user asks to commit changes or write a commit message.
Use when syncing all git repos under ~/code across machines, typically at end-of-day (push) or start-of-day (pull). Triggers on「同步代码」「code-sync」「下班同步」「上班更新」.
Use this skill when you need to perform Git operations such as committing changes, creating branches, merging, resolving conflicts, managing remotes, or any other Git-related tasks.
Capture AI agent sessions in your git workflow. Use for setup, rewinding to checkpoints, exploring session history, and troubleshooting.
Use when you need to work on multiple branches simultaneously, run parallel Claude Code sessions, handle emergency hotfixes during feature work, review PRs without switching branches, or test across branches without losing current work. Use when asked to "work on two branches at once", "parallel development", "switch without losing work", "create a worktree", or "hotfix while working on a feature".