Loading...
Loading...
Found 229 Skills
Automated git commit and push tool with AI-generated commit messages
Automatically creates comprehensive pull requests to the dev branch when user indicates their feature/fix is complete and ready for review. Use when user mentions creating PR, submitting for review, or indicates work is done. Examples - "create a PR", "ready for review", "open a pull request", "submit this to dev", "all tests passing, let's get this reviewed".
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.
Enforces Conventional Commits format when creating git commits. Use this skill whenever you need to create a commit message. Triggers on "commit", "git commit", "コミット", "変更をコミット".
Prepare commits and pull requests for this repo following the PR template and Conventional Commits.
A comprehensive Git agent skill combining strategic workflows, strict conventional commit standards, and safe execution protocols. Acts as a senior engineer to guide users through atomic, verifiable, and standardized git operations.
This skill should be used when creating conventional commits for current changes and then submitting the current branch as a pull request for code review. It combines the git:commit and git:submit-pr skills into a single workflow.
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".
Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices.
Helps users create standardized Git commits. Use this when users want to submit code, save changes, or create a commit.
Use this to write commit messages unless specific commit message conventions are explicitly specified.
Analyze git changes and generate conventional commit messages. Supports batch commits for multiple unrelated changes. Use when: (1) Creating git commits, (2) Reviewing staged changes, (3) Splitting large changesets into logical commits.