commit

Extract ticket IDs from branch names and commit changes with Japanese messages.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/NagasakaH/dev-process --skill commit-nagasakah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/NagasakaH/dev-process/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/NagasakaH/dev-process --skill commit-nagasakah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

コミットメッセージ作成を自動化し、ブランチ名に含まれるチケット情報を連携させて一貫した変更履歴を実現します。

Core Features & Use Cases

  • ブランチ名からチケットIDを抽出してMCPと連携し、チケット情報を取得します。
  • チケット情報と変更内容を組み合わせて日本語のコミットメッセージを自動生成します。
  • 変更を自動的にコミットし、プロジェクト管理ツールと連携したワークフローを支援します。

Quick Start

現在のブランチ名を確認し、抽出したチケットIDに基づく日本語のコミットメッセージを生成して、変更をコミットしてください。

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commit messages using a branch name with a ticket ID?

To automate git commit messages, this Skill extracts the ticket ID from your current branch name, queries connected MCPs for ticket details, and generates a contextual Japanese commit message. It validates ticket status before executing the commit automatically.

Can I fetch ticket details from MCPs before generating a Japanese commit message?

Yes, you can fetch ticket details from MCPs before generating a Japanese commit message. The Skill queries available MCPs using the ticket ID extracted from your branch name to retrieve context, ensuring the commit message accurately reflects the ticket.

What is the best way to link branch names to project management tickets for commits?

The best way to link branch names to project management tickets is by extracting the ticket ID directly from the branch metadata. This Skill automates that extraction, queries your ticketing system via MCP, and commits with a message referencing the retrieved ticket details.

Does this automated commit tool support multiple ticketing systems via MCP?

Yes, this automated commit tool supports multiple ticketing systems via MCP. It is designed to query any available MCP integration to fetch ticket details, validate the ticket status, and incorporate that context into the generated Japanese commit message.

Do I need MCP integrations configured to use this automated commit Skill?

Yes, you need MCP integrations configured to fully utilize this automated commit Skill. MCPs are required to query ticketing systems for detailed ticket information, which is then combined with your changes to generate meaningful Japanese commit messages.

Why should I use branch metadata for generating git commit messages?

Using branch metadata for generating git commit messages ensures consistent linkage between code changes and project management tickets. This Skill automates extracting ticket IDs from branches to validate status and produce structured Japanese commit messages without manual entry.