Git Workflow and Commit Rules

gitworkflowconventions

Git workflow conventions covering commit message format, branching strategy, and collaboration practices for consistent version control.

Целевые файлы

Файл	Формат
CLAUDE.md	markdown
.github/copilot-instructions.md	markdown

Содержимое

Commit message format: type(scope): description. Types: feat, fix, docs, style, refactor, test, chore, perf, ci. Example: "feat(auth): add OAuth2 login flow". Keep commits atomic — each commit should represent one logical change. Do not mix refactoring with feature work in the same commit. Write commit descriptions in imperative mood: "add feature" not "added feature" or "adds feature". Branch naming: type/short-description (e.g., feat/user-auth, fix/login-redirect, chore/update-deps). Use kebab-case. Always create feature branches from the latest main/master. Rebase before merging to keep history linear when possible. Pull requests must have a clear title, description of changes, and linked issue number. Request at least one review before merging. Never force-push to main/master or shared branches. Use --force-with-lease on personal branches only when necessary. Tag releases using semantic versioning: vMAJOR.MINOR.PATCH (e.g., v1.2.3). Write changelog entries for each release.

CLI

npx mindaxis apply git-conventions --target cursor --scope project

Используется в паках

Claude Code Power User

Master Claude Code CLI