git-workflow
Git best practices for commits, branches, pull requests, and collaboration workflows following Conventional Commits and GitFlow patterns
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Git Workflow Skill
Objective
Implement professional Git workflows ensuring clean commit history, proper branch management, effective collaboration, and code review best practices.
When to Use This Skill
Auto-invoke when:
- User mentions "commit", "push", "branch", "merge", "pull request", "PR"
- Before code changes need to be saved
- Preparing for deployment or release
- Resolving merge conflicts
Commit Message Standards (Conventional Commits)
Format: <type>(<scope>): <subject>
Types: feat, fix, docs, style, refactor, perf, test, chore, ci
Examples:
feat(auth): add OAuth2 login support
fix(api): handle null response in user endpoint
docs(readme): update installation instructions
Branch Naming: <type>/<ticket-id>-<description>
Examples:
feature/AUTH-123-oauth-integration
bugfix/CORE-456-fix-null-pointer
hotfix/PROD-789-critical-security-patch
GitFlow Workflow
Main: production, Develop: integration Features: branch from develop → merge to develop Releases: branch from develop → merge to main+develop Hotfixes: branch from main → merge to main+develop
Pre-Commit Checklist
# No secrets
git diff --cached | grep -iE "api[_-]?key|secret|password"
# Run quality gates
npm run lint && npm run typecheck && npm run test
Version History
- 1.0.0 (2025-01-03): Initial Git workflow skill
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-28
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!