# Commit Helper

> Generate clear, conventional commit messages from git diffs.

Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing commits.

- Page: https://ss33.ai/skills/nodnarbnitram/commit-helper-53620713732
- Publisher: nodnarbnitram
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [Source control & code review](https://ss33.ai/skills/category/software-development-t44z8z/source-control-and-code-review-jebezw)
- License: MIT
- Source: https://github.com/nodnarbnitram/claude-code-extensions/blob/35e7f7deae689e12b94f9c242b8f59efe0f66476/.claude/skills/commit-helper/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/nodnarbnitram/commit-helper-53620713732

# Commit Helper

Generate well-structured commit messages following conventional commit format.

## Instructions

1. Run `git diff --staged` to see staged changes
2. Analyze the changes to understand:
   - What files were modified
   - What type of change (feat, fix, refactor, docs, etc.)
   - The scope/component affected
3. Generate a commit message with:
   - Summary line under 50 characters
   - Type prefix (feat, fix, docs, refactor, test, chore)
   - Optional scope in parentheses
   - Detailed body explaining what and why

## Commit Types

- `feat`: New feature
- `fix`: Bug fix
- `docs`: Documentation changes
- `refactor`: Code restructuring without behavior change
- `test`: Adding or updating tests
- `chore`: Maintenance tasks

## Best Practices

- Use present tense ("Add feature" not "Added feature")
- Explain what and why, not how
- Keep summary concise but descriptive
- Reference issue numbers when applicable

## Example Output

```
feat(auth): add OAuth2 support for GitHub login

- Implement OAuth2 flow with PKCE
- Add token refresh mechanism
- Store tokens securely in encrypted storage

Closes #123
```