What problem does it solve?
Inconsistent Git workflows lead to messy, unreadable commit history, confusing code reviews, accidental data loss from unsafe force pushes, and friction when collaborating with team members on shared repositories.
Core Features & Use Cases
- Standardized Branch Naming: Enforces consistent feat/, fix/, and chore/ branch patterns to make repository structure immediately understandable.
- Conventional Commit Guidance: Provides clear rules for commit formatting to make change history scannable and automatable.
- Safe Merge & Rewrite Rules: Outlines when to squash, merge, or rebase, and enforces safe force-push practices to avoid disrupting shared branch history.
- Use Case: For example, when joining a new team project, use this skill to align your local Git workflow with team standards, avoid overwriting teammates' work, and ensure your pull requests are easy to review and merge.
Quick Start
Use the git-workflow skill to create a properly named feature branch for adding user authentication, write a compliant conventional commit for your initial changes, and select the appropriate merge strategy before opening a pull request for review.