create-commit

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

変更内容を分析して Conventional Commits 形式でコミットを作成します。

Analyze changes and create commits in Conventional Commits format.

bash

git status
git diff --staged

staged がない場合は

git diff

も確認してユーザーに staging を案内する。

bash

git status
git diff --staged

If there are no staged changes, also check

git diff

and guide the user to stage changes.

type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation-only changes
`refactor`	Code refactoring without functional changes
`test`	Adding or modifying tests
`chore`	Changes to build processes or auxiliary tools
`style`	Code style-only changes (whitespace, formatting, etc.)
`build`	Changes to build systems or external dependencies
`ci`	Changes to CI configuration
`perf`	Performance improvements

変更ファイルのパスから scope を推定する。複数にまたがる場合は省略可。

Estimate the scope from the path of changed files. Can be omitted if changes span multiple scopes.

フォーマット:

type(scope): subject

例:

feat(auth): ソーシャルログイン機能を追加
fix(api): レスポンスのエラーハンドリングを修正
refactor(ui): コンポーネント構造を整理

ユーザーに提案して確認を取る。

Format:

type(scope): subject

Examples:

feat(auth): Add social login functionality
fix(api): Fix response error handling
refactor(ui): Organize component structure

Propose to the user and get confirmation.

bash

git commit -m "$(cat <<'EOF'
type(scope): subject

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

重要:

--no-verify

は絶対に使用しない（pre-commit フックを迂回しない）。

bash

git commit -m "$(cat <<'EOF'
type(scope): subject

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

Important: Never use

--no-verify

(do not bypass pre-commit hooks).

Add
```
!
```
for breaking changes:
```
feat!: ...
```
or write
```
BREAKING CHANGE:
```
in the body
Subject should be in imperative and present tense (Japanese is allowed)
Subject should be within 72 characters
Warn and abort the commit if
```
.env
```
or authentication information files are included