git-ops
Use when performing git operations or generating smart commit messages - provides safe git workflow guidance, validation checks, and conventional commit formatting.
Works with
--- name: git-ops description: Use when performing git operations or generating smart commit messages - provides safe git workflow guidance, validation checks, and conventional commit formatting. license: MIT --- # Git Ops ## Overview Execute git operations safely while producing clear, conventional commit messages and workflow guidance. ## When to Use - Running git commands (status, add, commit, push, pull) - Generating smart commit messages - Managing branches and merges Avoid when: - The task is unrelated to git operations ## Quick Reference | Task | Load reference | | --- | --- | | Git operations | `skills/git-ops/references/git.md` | | **Branching Strategies** | `skills/git-ops/references/branching-strategies.md` | ## Workflow 1. Confirm repository state and intent. 2. Load the git operations reference. 3. Execute the command safely. 4. Provide status summary and next steps. ## Output - Operation result summary - Suggested follow-ups or warnings ## Common Mistakes - Running destructive commands without confirmation - Writing non-standard commit messages
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.
