Agent skill · writing content · aiskillstore
git-workflow
Git best practices for commits, branches, pull requests, and collaboration workflows following Conventional Commits and GitFlow patterns
Why this skill is useful
Codifies Git commit message standards and branch naming conventions that the AI could infer but now doesn't have to guess.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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: Branch Naming: <type>/<ticket-id>-<description> Examples: 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 Version History 1.0.0 (2025-01-03): Initial Git workflow skill
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/git-workflow--ea030d