git-conventions

What problem does it solve?

Inconsistent Git commit messages, branch naming, and workflow practices lead to messy repository history, difficult code reviews, and reduced team efficiency. This Skill provides clear, actionable guidelines to standardize Git usage across your team.

Core Features & Use Cases

• Conventional Commits: Learn the detailed format and types (feat, fix, docs, refactor, perf, etc.) for clear, automated changelog generation and improved commit readability.
• Branch Naming Conventions: Adopt standardized patterns (feature/, fix/, release/) for organized and traceable development, simplifying branch management.
• Workflow Patterns: Understand and implement popular Git workflows like Git Flow, GitHub Flow, and Trunk-Based Development to match your team's specific needs and deployment frequency.
• Use Case: A development team struggles with inconsistent commit history and merge conflicts. This Skill helps them adopt Conventional Commits and a structured branching strategy, improving code quality, simplifying releases, and streamlining onboarding for new members.

Quick Start

Example: Feature commit with body and footer

feat: add user authentication

Implement JWT-based authentication system with refresh tokens. Includes middleware for protected routes.

Closes #123