git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
Works with
--- name: git-workflow description: Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy. license: MIT --- # Git Workflow This skill provides universal Git workflow and conventional commits guidelines. See @REFERENCE.md for detailed documentation. ## Quick Reference - **Commits**: `<type>(<scope>): <description>` - **Types**: feat, fix, docs, style, refactor, perf, test, build, ci, chore - **Branches**: `feature/`, `fix/`, `refactor/`, `docs/` - **Max branch life**: 3 days - **Review**: Required before merge
More Git Workflows skills
git-commit
github/awesome-copilot
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
git-workflow-and-versioning
addyosmani/agent-skills
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
resolve-merge-conflicts
warpdotdev/common-skills
Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.
