Loading...
Loading...
Found 25 Skills
Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
This skill should be used when creating Git commits to ensure they follow the Conventional Commits specification. It provides guidance on commit message structure, types, scopes, and best practices for writing clear, consistent, and automated-friendly commit messages. Use when committing code changes or reviewing commit history.
Read this skill before making git commits
Create semantic git commits following best practices and Conventional Commits specification.
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.
Smart git commit workflow using Conventional Commits format with AI-generated commit message suggestions based on staged changes.
Generate well-formatted git commit messages following conventional commit standards
Cria mensagens de commit no estilo Conventional Commits — usar quando o usuário pede "commit", "git commit", ou após mudanças prontas para serem registradas no histórico.
Reference for Chinese Commit and Changelog Configuration - Chinese Adaptation of Conventional Commits, Chinese Templates for commitlint/husky/commitizen, Chinese Configuration for conventional-changelog. Only invoke when user explicitly uses /chinese-commit-conventions, do not trigger automatically based on context.
Git workflow guidance for commits, branches, and pull requests
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.
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.