Loading...
Loading...
Found 155 Skills
AUTOMATICALLY invoke this skill whenever git commit is needed - no user request required. Direct git commit will FAIL validation. This skill contains required pre-commit setup. Triggers: "커밋해", "커밋 ㄱㄱ", "커밋 만들어줘", "커밋 찍어줘", or ANY situation requiring git commit.
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.
Draft, rewrite, and validate Odoo-style commit messages using [TAG] module: summary format, 50/72 length limits, imperative English, WHY-first body, and correct tag selection. Includes optional migration tagging ([MIG]) when the project workflow (like OCA) uses it.
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.
Commit Message Formatter - Auto-activating skill for DevOps Basics. Triggers on: commit message formatter, commit message formatter Part of the DevOps Basics skill category.
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.
Generate professional git commit messages following cbea.ms guidelines. Outputs plain copy-pasteable commit message text by default.
Generate appropriate commit messages based on Git diffs
Generate conventional commit messages based on git diff analysis. Use when you need to create well-structured commit messages following conventional commit format.
Auto-generates conventional commit messages from git diffs with tiered format enforcement. Analyzes staged changes to produce meaningful commit messages following Conventional Commits specification.
Generates conventional commit messages by analyzing git diffs and changes. Use when writing commit messages, following commit conventions, or documenting changes.