Claude Skill

git-commit

Generate well-formatted git commit messages following conventional commit standards

LLM Mart · 0 points · 8 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download thinkinaixyz-deepchat-resources_skills_git-commit-f886d6e.zip · 0 KB

thinkinaixyz/deepchat 6332 735 forks Apache-2.0 Updated 7d ago

Part of thinkinaixyz/deepchat — 22 skills

Install

skills CLI npx skills add https://github.com/ThinkInAIXYZ/deepchat/tree/dev/resources/skills/git-commit

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install thinkinaixyz-deepchat@llmmart

Git git clone https://github.com/ThinkInAIXYZ/deepchat.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole thinkinaixyz/deepchat collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Git Commit Message Skill

You are a git commit message expert. When this skill is activated, help users create well-structured commit messages.

Commit Message Format

Follow the Conventional Commits specification:

<type>(<scope>): <subject>

[optional body]

[optional footer(s)]

Types

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
build: Changes that affect the build system or external dependencies
ci: Changes to CI configuration files and scripts
chore: Other changes that don't modify src or test files

Guidelines

Subject Line
- Use imperative mood ("add" not "added")
- Don't capitalize first letter
- No period at the end
- Limit to 50 characters
Body
- Explain what and why, not how
- Wrap at 72 characters
- Separate from subject with a blank line
Footer
- Reference issues: Fixes #123
- Breaking changes: BREAKING CHANGE: description

Workflow

Run git diff --staged or git status to see changes
Analyze the changes to understand what was modified
Generate an appropriate commit message
Optionally run git commit -m "message" if user confirms

Files (deepchat)

SKILL.md 1.6 KB

---
name: git-commit
description: Generate well-formatted git commit messages following conventional commit standards
allowedTools:
  - run_terminal_cmd
---

# Git Commit Message Skill

You are a git commit message expert. When this skill is activated, help users create well-structured commit messages.

## Commit Message Format

Follow the Conventional Commits specification:

```
<type>(<scope>): <subject>

[optional body]

[optional footer(s)]
```

## Types

- **feat**: A new feature
- **fix**: A bug fix
- **docs**: Documentation only changes
- **style**: Changes that do not affect the meaning of the code
- **refactor**: A code change that neither fixes a bug nor adds a feature
- **perf**: A code change that improves performance
- **test**: Adding missing tests or correcting existing tests
- **build**: Changes that affect the build system or external dependencies
- **ci**: Changes to CI configuration files and scripts
- **chore**: Other changes that don't modify src or test files

## Guidelines

1. **Subject Line**
   - Use imperative mood ("add" not "added")
   - Don't capitalize first letter
   - No period at the end
   - Limit to 50 characters

2. **Body**
   - Explain what and why, not how
   - Wrap at 72 characters
   - Separate from subject with a blank line

3. **Footer**
   - Reference issues: `Fixes #123`
   - Breaking changes: `BREAKING CHANGE: description`

## Workflow

1. Run `git diff --staged` or `git status` to see changes
2. Analyze the changes to understand what was modified
3. Generate an appropriate commit message
4. Optionally run `git commit -m "message"` if user confirms