Loading...
Loading...
Found 38 Skills
Read this skill before creating any git commit to ensure the commit message matches the project's established patterns. Triggers on: git commit, /commit, creating commits, or any task that results in a git commit.
Auto-generates conventional commit messages from git diffs with tiered format enforcement. Analyzes staged changes to produce meaningful commit messages following Conventional Commits specification.
Conventional Commits specification. Covers commit structure, types, breaking changes. Keywords: feat, fix, BREAKING CHANGE.
Generate professional git commit messages following cbea.ms guidelines. Outputs plain copy-pasteable commit message text by default.
Enforces Conventional Commits format when creating git commits. Use this skill whenever you need to create a commit message. Triggers on "commit", "git commit", "コミット", "変更をコミット".
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.
Guidance for writing git commit messages that follow the Conventional Commits 1.0.0 specification. Use when preparing commit messages, summarizing code changes for a commit, or validating commit text for compliance.
Drafts and validates Git commit messages that follow the Conventional Commits specification and use Chinese as the primary commit language. Use when writing, reviewing, or fixing commit messages; choosing types or scopes; marking breaking changes; adding bodies or issue footers.
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so `git log` alone tells the story. User-invoked: run it after a commit.
Generate concise Git commit messages in imperative mood. Analyzes staged changes first; if none, examines unstaged and untracked files. Use when the user asks to create, write, draft, make, or generate a commit message.
Use when creating git commits, writing commit messages, or following version control workflows
Draft and validate commit messages that comply with Conventional Commits 1.0.0. Use when writing git commit messages, enforcing commit format in reviews/CI, mapping commits to SemVer intent, or converting plain-language change notes into spec-compliant messages with optional scope, body, footers, and breaking-change markers.