git-workflow

Branch naming conventions organize feature work and bug fixes using prefixes like feat/AI-XXXX-description for features, fix/description for bugs, and chore/description for maintenance. This Skill enforces these patterns across your team, making branch history readable and enabling automated CI checks to validate branch names before code is pushed.

Conventional commits format (feat:, fix:, docs:, etc.) keeps commit history readable and automatable for release notes and versioning. This Skill codifies that standard, so every team member writes meaningful messages like 'feat: add feature X' or 'fix: resolve bug Y', making the project history traceable and actionable.

PR templates and CI checks catch formatting, linting, type errors, and test failures before code reaches main. This Skill monitors CI status and validates that branches follow naming conventions and commits match conventional format, ensuring only quality code passes through code review and deployment pipelines.

Yes. This Skill applies standardized Git workflows across all work types—features, bug fixes, chores, and code reviews—with branch prefixes and commit conventions tailored to each. It works across development, testing, and deployment stages, so the entire team follows one coherent process.

Quality gates verify formatting and naming conventions before commits and PRs are created. If a branch or message violates the standard, the check fails and shows what correction is needed, preventing non-standard work from entering the pipeline and keeping history clean.