Git Workflow
Branching strategies, conventional commits, merge vs rebase, PR workflow, and conflict resolution in one reference.
- What
- Branching strategies, conventional commits, merge vs rebase, PR workflow, and conflict resolution in one reference.
- Cost
- Free
- Needs
- the Muse app (mobile or web), and a git repository you work with. No installation, no API key. A knowledge reference.
- Level
- Beginner — the Muse app (mobile or web)…
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a complete Git workflow reference for teams of all sizes. Three branching strategies compared (GitHub Flow for continuous deployment, trunk-based for high-velocity teams with feature flags, GitFlow for scheduled enterprise releases) with a when-to-use table. Conventional Commits format with the type table (feat, fix, docs, style, refactor, test, chore, perf, ci, revert), good vs bad examples, and a commit message template. Merge vs rebase explained with rules (merge preserves history for shared branches, rebase for clean local history, never rebase pushed shared branches). PR workflow with title format, description template, reviewer and author checklists. Conflict resolution (identify, resolve manually or with mergetool, accept one side), plus prevention strategies. Branch naming conventions and cleanup commands, stash workflow, semantic versioning and releases with tags, changelog generation, essential git configs and aliases, gitignore patterns, undoing mistakes (reset, revert, amend), git hooks examples, anti-patterns, and a quick reference table. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: a pure knowledge reference, nothing to install; team conventions should be agreed together, not imposed. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Git Workflow is a free Muse skill and complete Git workflow reference for teams of all sizes. Three branching strategies are compared, GitHub Flow for continuous deployment, trunk-based for high-velocity teams with feature flags, and GitFlow for scheduled enterprise releases, with a when-to-use table. It also covers Conventional Commits, merge versus rebase, and PR workflow.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Git Workflow" with your Muse. Prerequisites: the Muse app (mobile or web), and a git repository you work with. No installation, no API key. A knowledge reference. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/git-workflow/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Help me set up our git workflow: [team size, release cadence, e.g. 4 devs shipping weekly]. Recommend a branching strategy and commit conventions." 3. Ask Muse to draft the .gitmessage template, the PR description template, and the branch naming rules for your team, then review together. Tip: pick the simplest strategy that fits. Most teams should start with GitHub Flow and only reach for GitFlow when release trains demand it. Safety: a skill is plain-text instructions; it runs nothing by itself. Never force-push shared branches, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.