Loading...
Loading...
Found 347 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.
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing PRs, use github-pr-merge instead.
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」「下班同步」「上班更新」.
Safely clean merged and stale git branches with explicit confirmations.
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.
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.
Generate clear, conventional commit messages from staged changes. Use when the user asks to commit or needs a commit message.
Generates properly formatted Git commit messages (title + description) following Conventional Commits. Use this skill whenever the user wants to write a commit message, document code changes in git format, or asks things like "how should I commit this?", "write a commit for these changes", "help me with my commit message", or describes what they changed and needs a git-ready output. Always use this skill when the user describes code changes and needs a commit, even if they don't explicitly say "commit".
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.