git-workflow
>-
Works with
--- name: git-workflow description: >- license: MIT --- # Git Workflow Use this skill whenever the user asks to: - commit these changes - create a commit - save my work - stage and commit - commit current work - create a branch - start a feature branch - make a branch for this work - start working on a change - create a PR - open a PR - draft a PR - prepare a pull request - commit and open a PR - create a branch and PR - submit the current work ______________________________________________________________________ ## Shared references Before executing any workflow, load all four shared references: - [Scope Detection](shared/scope-detection.md) - [File Inclusion Policy](shared/file-inclusion-policy.md) - [Safety Rules](shared/safety-rules.md) - [Conventional Types](shared/conventional-types.md) ______________________________________________________________________ ## Intent routing Based on the user's request, load exactly one workflow doc: | User intent | Load | | ----------------------------------------------- | -------------------------------- | | Commit work, save changes, stage and commit | [docs/commit.md](docs/commit.md) | | Create a branch, start a feature branch | [docs/branch.md](docs/branch.md) | | Create/open/draft a PR, submit the current work | [docs/pr.md](docs/pr.md) | When intent is ambiguous, prefer the more complete workflow. If the user says "commit and open a PR", load `docs/pr.md` — it covers the full lifecycle including commit and branch.
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.
