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
- Use "Git Workflow" with your Muse.
- 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:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
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://github.com/affaan-m/ECC/blob/main/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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.