コミット

Analyze Git changes and create Conventional Commits in Japanese.

Updated Dec 28, 2023
One-click install
npx skills add https://github.com/daisuke-tanabe/daisuke-tanabe --skill -daisuke-tanabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: コミット
Source: https://github.com/daisuke-tanabe/daisuke-tanabe/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/daisuke-tanabe/daisuke-tanabe --skill -daisuke-tanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of analyzing code changes and creating well-defined, logically grouped commits, ensuring a clean and understandable Git history.

Core Features & Use Cases

  • Change Analysis: Reviews git status and git diff to understand modifications.
  • Logical Grouping: Organizes related changes into distinct commit units based on functionality (e.g., feature additions, bug fixes).
  • Conventional Commits: Enforces a structured commit message format for better readability and automation.
  • Security Check: Identifies and warns about potential inclusion of sensitive information in commits.
  • Use Case: After making several unrelated changes to a project, use this Skill to automatically group them into separate, meaningful commits, each addressing a specific logical change.

Quick Start

Analyze the current changes and create commits following the Conventional Commits format.

Frequently Asked Questions about コミット

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

FAQPage Schema
How do I group unrelated code changes into separate logical commits?

To group unrelated code changes into separate logical commits, this Skill analyzes git diff and status output, categorizes modifications by type, and generates individual commits for each functional change.

Can I enforce Conventional Commits format for my git history?

Yes, you can enforce Conventional Commits format by automatically generating structured commit messages in Japanese, categorizing changes as features, bugfixes, or refactors for improved history readability.

What is the best way to prevent sensitive information from being committed to version control?

To prevent sensitive information from being committed to version control, this Skill performs security checks on your staged changes, identifies potential secrets, and warns you before finalizing the commit.

Does this commit creation process work without additional dependencies?

Yes, the commit creation process works without additional dependencies, analyzing your current development workflow changes directly to build logically structured commit units.

How to create structured commit messages after making several mixed code modifications?

To create structured commit messages after mixed code modifications, the tool reviews your modifications, groups related changes into distinct units by functionality, and commits them individually.