# Git Workflow

> Git branching and commit message conventions Use when this capability is needed.

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

---


# Git Workflow

## Branch naming

- Feature branches: `feat/<short-description>`
- Bug fixes: `fix/<short-description>`
- Chores: `chore/<short-description>`

## Commit messages

Use conventional commits: `type(scope): description`

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

Examples:
- `feat(auth): add OAuth2 login flow`
- `fix(api): handle null response from upstream`

## Rules

- Never force-push to `main` or `master`
- Always create a branch for changes — never commit directly to main
- Keep commits atomic — one logical change per commit
- Write commit messages in imperative mood ("add feature" not "added feature")
- Rebase feature branches on main before merging

---
> Source: [NinetrixAI/Ninetrix](https://github.com/NinetrixAI/Ninetrix) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-16 -->