メニュー
Generate conventional commit messages by analyzing staged git changes. Detects change type, suggests scope, and formats messages following the Conventional Commits specification.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/platxa/platxa-skill-generator --skill commit-messageコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Autonomous skill creator for Claude Code CLI. Use when the user asks to "create a skill", "generate a skill", or "build a new slash command". Uses multi-phase orchestrated workflow with Task tool subagents to research domains, design architecture, generate content, validate quality, and iteratively improve via eval infrastructure. Creates production-ready skills following the Agent Skills open standard and Claude Code extensions.
Automatically generates and improves code documentation across Python, JavaScript/TypeScript, Java, Go, and Rust. Detects language conventions, applies appropriate docstring standards, and validates documentation quality.
Guide for structured error handling across Platxa stack. Covers error types, retry patterns with exponential backoff, logging, and HTTP response mapping for Python, TypeScript, and Go.
SKILL.md を表示中
SOC 職業分類に基づく
| name | commit-message |
| description | Generate conventional commit messages by analyzing staged git changes. Detects change type, suggests scope, and formats messages following the Conventional Commits specification. |
| allowed-tools | ["Read","Bash","Grep","Glob"] |
| metadata | {"version":"1.0.0","tags":["automation","git","workflow"]} |
| user-invocable | true |
Generate conventional commit messages from staged git changes.
This skill automates commit message generation for development teams. It analyzes staged changes, detects the appropriate commit type (feat, fix, refactor, etc.), suggests a scope based on modified files, and generates a properly formatted message following the Conventional Commits specification.
What it automates:
Time saved: ~2-5 minutes per commit
Run this skill when:
First, I'll examine what's staged:
git diff --cached --stat
git diff --cached --name-status
This shows:
Based on the changes, I'll determine the appropriate type:
| Pattern | Type | Description |
|---|---|---|
| New feature files | feat | New functionality |
| Bug fix in existing code | fix | Bug repair |
| Code restructuring | refactor | No behavior change |
| Performance improvements | perf | Faster/leaner code |
| Test additions/changes | test | Test updates |
| Documentation only | docs | Documentation |
| Formatting/style | style | No code change |
| Build/CI config | build/ci | Infrastructure |
| Maintenance | chore | Other changes |
Extract scope from the primary changed directory:
src/api/* → scope: apisrc/components/* → scope: componentslib/utils/* → scope: utilsFormat following Conventional Commits:
<type>(<scope>): <description>
<body - explains why, not how>
<footer - issues, breaking changes>
Subject line rules:
Present the generated message for your approval, then execute:
git commit -m "<message>"
Before committing, I verify:
User: Generate a commit message for my staged changes
Assistant: Analyzing staged changes...
git diff --cached --name-status:
A src/components/Button.tsx
M src/components/index.ts
Detected: New component file added
Type: feat
Scope: components
Generated message:
feat(components): add Button component
Proceed with this commit? (y/n)
User: /commit - this fixes issue #42
Assistant: Analyzing staged changes...
git diff --cached --name-status:
M src/utils/parser.ts
Detected: Modified existing utility code
Type: fix
Scope: utils
Generated message:
fix(utils): resolve array parsing edge case
Handle empty arrays correctly in parser to prevent
undefined errors when processing user input.
Closes #42
Proceed with this commit? (y/n)
User: Generate commit - this changes the API signature
Assistant: Analyzing staged changes...
git diff --cached --name-status:
M src/api/auth.ts
M src/types/auth.ts
Detected: API modification with signature change
Type: feat (with breaking change)
Scope: api
Generated message:
feat(api)!: update authentication flow
Migrate from session-based to JWT authentication.
This changes the login endpoint response format.
BREAKING CHANGE: login() now returns {token, refreshToken}
instead of {sessionId}. All clients must update their
authentication handling.
Proceed with this commit? (y/n)
| Type | When to Use | SemVer Impact |
|---|---|---|
feat | New feature | Minor bump |
fix | Bug fix | Patch bump |
docs | Documentation only | None |
style | Formatting, no code change | None |
refactor | Code restructure, no behavior change | None |
perf | Performance improvement | None |
test | Adding/updating tests | None |
build | Build system changes | None |
ci | CI configuration | None |
chore | Maintenance tasks | None |
Add ! after type/scope or include footer:
feat!: change APIfeat(api)!: update endpointBREAKING CHANGE: descriptionBefore finalizing a commit message: