Loading...
Loading...
Found 36 Skills
Create semantic git commits following Conventional Commits specification. Use when committing changes, making commits, or when asked to commit.
Generates conventional commit messages by analyzing git diffs and changes. Use when writing commit messages, following commit conventions, or documenting changes.
Auto-generates conventional commit messages from git diffs with tiered format enforcement. Analyzes staged changes to produce meaningful commit messages following Conventional Commits specification.
Generate concise, descriptive git commit messages following best practices. Use when creating git commits from staged changes, crafting commit messages, or reviewing commit message quality. Use when the user says /commit or asks to create a git commit.
This skill MUST be loaded on every git commit without exception. It should also be used when the user asks to "write a conventional commit", "format a commit message", "follow conventional commits spec", "create a semantic commit", "make a commit", "commit changes", or "git commit". Every commit message produced in this project MUST conform to this specification.
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Generate well-formatted git commit messages following conventional commit standards
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarize my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.
Generate high-quality git commit messages following Conventional Commits and Chris Beams' Seven Rules. Infers WHY from context and provides clear guidance on structure, scope, and body content.
Create standardized git commit messages. Prioritize following the project's existing commit conventions, and support the Conventional Commits format. Usage scenarios: Users request to create commits or write commit messages
Commit Message Specification. Generate commit messages compliant with Conventional Commits based on staged changes, support Chinese descriptions, and automatically handle types, scopes, and breaking changes. Use to write standardized commit messages from staged git changes.
Generate a git-log-review-friendly commit message from repository changes. Use when you need to inspect staged changes, the current working tree relative to `HEAD`, or a commit-to-working-tree range and draft only the commit message text in a conventional-commit-style format, without creating the commit. Trigger for requests such as the skill `git:message`, the skill `git:message` with `staged`, the skill `git:message` with `HEAD`, or the skill `git:message` with `<commit>`, especially when the user wants a squash-ready summary of the most important changes.