# Git Commit

> Create well-structured git commits with conventional commit messages, proper staging, and commit best practices. Use when this capability is needed.

- Skill: `tomevault-io/git-commit-24` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/git-commit-24`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/git-commit-24/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/git-commit-24

---


# Git Commit Helper

This skill helps create professional, well-structured git commits following best practices.

## Commit Message Format

Use conventional commit format:

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

[optional body]

[optional footer]
```

### Types

- **feat**: New feature
- **fix**: Bug fix
- **docs**: Documentation changes
- **style**: Code style changes (formatting, etc.)
- **refactor**: Code refactoring
- **test**: Adding or modifying tests
- **chore**: Maintenance tasks

## Workflow

1. Run `git status` to see changes
2. Run `git diff` to review what changed
3. Stage appropriate files (prefer specific files over `git add .`)
4. Create commit with descriptive message
5. Verify commit was successful

## Best Practices

- Keep commits atomic (one logical change per commit)
- Write clear, descriptive commit messages
- Don't commit sensitive files (.env, credentials)
- Review changes before committing

## Examples

- "Commit my changes with a good message"
- "Create a commit for the login feature"
- "Stage and commit the bug fix"

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/accomplish-ai) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->