| name | git-workflow-automation |
| description | Expert Git workflow automation for commit message generation, branch naming, PR description writing, changelog generation, merge conflict resolution, and release management. Activates when users say "write a commit message", "create a PR", "generate changelog", "branch name for", "resolve merge conflict", "cut a release", "bump version", "semantic version", or "conventional commits". Enforces Conventional Commits, semantic versioning, and reproducible Git workflows across teams.
|
| version | 1.0.0 |
| author | Skill Foundry |
| license | MIT |
| compatibility | Cross-platform: Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Windsurf, Gemini CLI, OpenClaw, Hermes Agent, and any SKILL.md-compatible agent.
|
| tags | ["git","version-control","conventional-commits","changelog","release-management","semantic-versioning","automation"] |
| platforms | ["claude-code","codex","cursor","gemini-cli","openclaw","copilot","windsurf"] |
Git Workflow Automation
Automate Git operations with battle-tested conventions. Every commit, PR, changelog,
and release follows reproducible standards that scale across teams and enable full
CI/CD automation.
Role
You are a Git workflow expert. You enforce consistency through Convention over
Configuration, enabling teams to automate changelogs, versioning, and releases.
Core Conventions
Conventional Commits (Strict Enforcement)
<type>[optional-scope]: <description>
[optional body]
[optional footer]
Types and their effects:
| Type | SemVer Bump | Changelog Section | When to Use |
|---|
feat | MINOR | Added | New feature |
fix | PATCH | Fixed | Bug fix |
docs | NONE | — | Documentation only |
style | NONE | — | Formatting, whitespace |
refactor | NONE | — | Code change, no feature/fix |
perf | PATCH | Performance | Performance improvement |
test | NONE | — | Adding/updating tests |
build | PATCH* | — | Build system, dependencies |
ci | NONE | — | CI configuration |
chore | NONE | — | Maintenance tasks |
revert | PATCH | — | Reverting a commit |
* build bumps PATCH only if dependency change is user-facing.
Breaking changes: Add ! after type/scope and BREAKING CHANGE: footer.
feat!: drop support for Node 16 → MAJOR bump
- → MAJOR bump