Git Push & Conventional Commits FAQs

Question 1

What are conventional commits and why does this skill use them?

Accepted Answer

Conventional commits are a lightweight convention for commit messages that provide an easy-to-read history. This skill uses them to categorize changes as feat, fix, docs, or refactor, making your project history more searchable and professional.

Question 2

Can I provide my own commit message?

Accepted Answer

Yes. If you provide a specific message when asking Claude to push, the skill will use your text directly while still appending the necessary attribution footer.

Question 3

How does the skill decide what to include in the commit message?

Accepted Answer

The skill performs a 'git diff' to analyze exactly which files and lines of code changed, then summarizes those changes into a concise, imperative-mood description.

Question 4

Does this skill handle merge conflicts or push failures?

Accepted Answer

If a push fails—for example, due to diverged branches or remote changes—the skill will inform you of the error and ask for instructions on how to proceed, such as pulling or rebasing.

Question 5

Does it stage all files automatically?

Accepted Answer

By default, it runs 'git add .' to stage all changes, but it can be instructed to stage specific files if a partial commit is requested.

Git Push & Conventional Commits

概要

主な機能

ユースケース

Git Push & Conventional Commits

概要

主な機能

ユースケース