# Commit

> Create well-structured git commits following conventional commit format. Use when the user asks to commit changes, create a commit, or save their work to git. Use when this capability is needed.

- Skill: `tomevault-io/commit-66` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/commit-66`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/commit-66/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/commit-66

---

# Commit Skill

Create commits following the project's conventional commit format.

## Commit Format

```
<type>[(scope)]: Subject
```

**Types:** `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `deps`

**Changelog types:** `build`, `deps`, `feat`, `fix`, `refactor`

## Process

1. Run `git status` to see changes
2. Run `git diff --staged` and `git diff` to understand changes
3. Analyze all changes and draft commit message:
   - Summarize the nature (feat, fix, refactor, etc.)
   - Focus on "why" rather than "what"
   - Keep subject under 72 characters
4. Stage specific files (avoid `git add -A`)
5. Create commit with conventional format
6. Verify with `git status`

## Guidelines

- Never commit sensitive files (.env, credentials)
- Stage specific files rather than using `git add -A`
- One logical change per commit
- Subject should complete: "If applied, this commit will..."

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