# Generate Conventional Commit Messages

Writing clear commit messages from complex diffs can slow reviews. This skill inspects Git changes and drafts Conventional Commit messages with suggested file groups.

## Install

```bash
npx skillstore add daisuke897/commit-message-generator
```

## Metadata

- Status: approved
- Slug: daisuke897-commit-message-generator
- Skillstore revision: r1
- Version status: missing
- Tree hash: 3309df32e0236212754ba76da08038b6f721cae342e57b829170041609cc2fff
- Author: Daisuke897
- GitHub username: Daisuke897
- License: MIT
- Repository: https://github.com/Daisuke897/dotfiles/tree/main/.github/skills/commit-message-generator
- Ref: 7e9e368dc1a370f2040369ebcd0db06d90cb48e5
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/daisuke897-commit-message-generator
- Manifest: https://skillstore.pages.dev/api/skills/daisuke897-commit-message-generator/manifest

## Capabilities

- Checks changed files with git status.
- Reads staged or unstaged diffs with git diff.
- Creates English Conventional Commit headers and bullet summaries.
- Suggests logical commit splits when changes span multiple concerns.
- Provides git add and git commit command suggestions for user review.

## Use Cases

- Prepare Clean Commits: Generate a clear message before committing staged changes.
- Split Mixed Changes: Identify separate commit groups when one diff covers several concerns.
- Improve Review Context: Turn file changes into concise commit summaries for team review.

## Prompt Templates

### Draft Basic Message

```
Generate a Conventional Commit message for my current Git changes. Keep it in English and do not commit anything.
```

### Use Staged Changes

```
Review my staged changes and suggest one Conventional Commit message with a short bullet summary.
```

### Check Commit Split

```
Analyze my Git diff and tell me whether these changes should be split into multiple commits. Include target files and messages.
```

### Apply Project Rules

```
Generate commit suggestions that follow Conventional Commits and these project rules: [add rules]. Include rationale for any split.
```

## Limitations

- It does not execute git commit or git push.
- It depends on available Git diff context.
- It cannot verify project-specific commit rules unless provided.
- It may need user judgment when a diff contains unrelated changes.

## Best Practices

- Stage related files before asking for a final message.
- Share project commit conventions when they differ from Conventional Commits.
- Review suggested file groups before copying any command.

## Anti Patterns

- Do not ask it to commit or push changes.
- Do not combine unrelated features and refactors into one commit.
- Do not accept a message without checking sensitive diff content.

## Security Audit

- Audited at: 2026-07-05T09:12:50.03\+00:00
- Summary: The four static findings are false positives caused by Markdown backticks around Git commands. The skill uses fixed Git inspection commands to build commit suggestions and explicitly forbids running commit or push. No prompt injection or data exfiltration intent was found.

## Stats

- Views: 225
- Downloads: 13
- Favorites: 0
- Popularity score: 0