Use this skill when the user needs help formatting git commit messages according to Conventional Commits specification. Provides guidance on commit types, scope, and message structure.
Skills（SKILL.md）は、AIエージェント（Claude Code、Cursor、Codexなど）に特定の能力を追加するための設定ファイルです。
詳しく見る →Use this skill when the user needs help formatting git commit messages according to Conventional Commits specification. Provides guidance on commit types, scope, and message structure.
**Format**: `<type>[scope]: <description>` + mandatory body + optional footers
コミットメッセージとPR作成のガイドライン
Help create git commits and PRs with properly formatted messages and release notes following CockroachDB conventions. Use when committing changes or creating pull requests.
Generates clear, conventional commit messages from git diffs
**Reference files**: `.deepwork/jobs/commit/job.yml`, `.deepwork/jobs/commit/steps/lint.md`
Generate standards-compliant commit messages following Conventional Commits with emojis. Use this when creating commits, reviewing commit messages, or ensuring consistent commit history.
Formats Git commit messages following Conventional Commits conventions. Use when the user asks to commit, write a commit message, format commits, or mentions conventional commits, staged changes, or release notes.
Generate conventional commit messages following best practices. Use when creating structured git commit messages.
Gitコミットメッセージの作成ガイドライン。コミット作成時、`git commit`実行時、またはユーザーがコミットメッセージの書き方について質問した際に使用する。日本語でのコミットメッセージ作成ルールを提供。
Write clear and concise commit messages that accurately describe the changes made in the codebase
コミットメッセージの命名規則を設定する。「コミットメッセージ設定」「コミット規則」「コミット形式を設定」「コミットメッセージルール」「commit message 設定」「コミットの書き方を設定」「コミットフォーマット」などで起動。プロジェクト固有のコミットメッセージルールを管理。
[コミット] 日本語コミットメッセージを生成（ステージ差分）
View and analyze commits in GitHub repositories - commit history, diffs, and commit details using gh CLI
Generates conventional commit messages. Use when creating git commits or reviewing staged changes. Ensures NO AI attribution in commits.
>
>
Prepare git commit messages following conventional commits. Activates on: commit, prepare commit, commit this, commit message, ready to commit, stage and commit
**Reference files**: `.deepwork/jobs/commit/job.yml`, `.deepwork/jobs/commit/steps/review.md`
Reviews changed code for issues, DRY opportunities, naming clarity, and test coverage using a sub-agent. Use as the first step before testing.
Create comprehensive commit message from spec phases and commit all changes
Generate descriptive commit messages by analyzing git diffs, very fast and context pollution safe. Use on any request to commit staged changes.
commit
commit-standards
Use when planning commit strategies or determining when to commit changes. Helps developers commit early and often to tell the story of their development process.
Validates commit messages against Conventional Commits specification using programmatic validation. Replaces the git-conventional-commit-messages text file with a tool that provides instant feedback.
커밋 메시지 작성 가이드 (한글/영어). 커밋 생성 시 자동으로 활성화되어 규칙을 준수하도록 안내합니다.
Create final git commit with requirement traceability tags (REQ-*). Use after refactor-phase to finalize TDD cycle with proper requirement linkage for bidirectional traceability.
Create single atomic commit with proper message format, issue linking, and pre-commit hook validation for WescoBar workflows
Complete workflow for creating commits following project standards.
Expert at crafting clear, meaningful git commit messages following conventional commit standards and repository conventions. Use when user asks to create commit messages, write commits, or needs help with git commit text. Analyzes git diffs and repository history to generate contextual, well-structured commit messages.
When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.
This skill supports three modes: **Create**, **Update**, and **Find**.
Extract and track commitments from meeting notes - who promised what to whom, with deadlines and status tracking.
Extract and track builder commitments from critique exegesis. Use /commitments to audit promises made in prose, verify implementation status, and identify unfulfilled obligations.
Generate a concise commit message by analyzing git diff changes
Conventional Commits specification. Covers commit structure, types, breaking changes. Keywords: feat, fix, BREAKING CHANGE.
This skill provides comprehensive guidance for creating git commits safely and effectively.
Use this skill when committing code changes, creating git commits, staging files for commit, or when the user asks to commit, save changes, or make a commit. Handles conventional commit format, explicit file staging, and commit message crafting.
**Every commit message uses conventional commits with gitmoji.** The format is consistent, scannable, and conveys intent at a glance.
'Creates well-structured git commits following conventional commit format. Use when committing changes, preparing commits, or when asked to commit code.'
Application security testing coordinator for common vulnerability patterns including XSS, injection flaws, and client-side security issues. Orchestrates specialized testing agents to identify and validate common application security weaknesses.
<purpose>
Reviews common RMS Go patterns including caching, retry logic, enums, and unmarshalling. Use when implementing utility patterns, seeing repeated boilerplate, or reviewing pattern usage.
Step-by-step guides for common development tasks like adding constructs, creating packages, and using workspace packages. Use when performing routine development tasks.
Shared utilities for Gemini-based skills including API key management, Vertex AI configuration, and client helpers. Use as dependency for skills requiring Gemini API access.
Use when parsing or generating Markdown following the CommonMark specification - AST structure, block/inline elements, and extensions
Communication coaching for working with a C (The Analyst) DISC type — precise, detail-oriented, quality-focused. Covers do's, don'ts, meetings, email, feedback, and conflict. Powered by Crystal's DISC framework.
Communication coaching for working with a D (The Captain) DISC type — direct, decisive, results-driven. Covers do's, don'ts, meetings, email, feedback, and conflict. Powered by Crystal's DISC framework.
Communication coaching for working with an SC (The Stabilizer) DISC type — consistent, thorough, practical. Covers do's, don'ts, meetings, email, feedback, and conflict. Powered by Crystal's DISC framework.