# Git Workflow

> Use when making changes that should be committed. Enforces atomic commits, meaningful messages, and clean history.

- Skill: `voidful/git-workflow` (Agent Skill)
- Install (CLI): `npx skillmds@latest add voidful/git-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/voidful/git-workflow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- License: Apache-2.0
- Author: voidful (https://skillmd.com/u/voidful)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/voidful/git-workflow

---


# Git Workflow

## Core Principle

Each commit should represent one logical change. If you cannot describe the commit in one sentence, it is too large.

## Commit Message Format

```
<type>: <description>

<optional body explaining why, not what>
```

Types: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`.

## Before Committing

1. Run `cargo test`. All tests must pass.
2. Run `cargo clippy`. No warnings.
3. Run `cargo fmt --check`. Code is formatted.
4. Review the diff: `git diff --cached`. Every changed line should relate to the commit message.

## Atomic Commits

- Separate refactoring from feature work. Refactor first, commit, then add the feature.
- Separate test additions from implementation. Add the test (it fails), commit. Implement (it passes), commit.
- Never mix documentation changes with code changes in the same commit.

## Aixlarity-Specific Rules

- The `--git` flag in `aixlarity exec` auto-commits after the session. Use it only when the task is self-contained.
- For multi-step tasks, prefer manual commits between steps.