Git Workflow and Versioning
Trunk-based development, atomic commits, clean branching, semantic releases and changelogs — git as your safety net
- What
- Trunk-based development, atomic commits, clean branching, semantic releases and changelogs — git as your safety net
- Cost
- Free
- Needs
- a git repository
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a git discipline skill from Addy Osmani's engineering workflow collection, written for the AI-agent era: with agents generating code at high speed, disciplined version control is what keeps changes manageable, reviewable, and reversible. It recommends trunk-based development (main always deployable, short-lived branches merged within 1–3 days, feature flags over long branches), commit-early-commit-often as save points, splitting messy working trees into atomic commits, and semantic versioning with changelogs for releases. Distinct from the already-published addyosmani skills — none of them cover version control. By @addyosmani, listed here with credit to its creator. Honest caveats: it's opinionated (trunk-based by default) — teams on gitflow can adapt the commit discipline, but the skill won't hide its preference; and no workflow survives an agent that force-pushes to main. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a git repository Install "Git Workflow and Versioning" for me. Trunk-based development, atomic commits, clean branching, semantic releases and changelogs — git as your safety net Repository: https://github.com/addyosmani/agent-skills/blob/main/skills/git-workflow-and-versioning/SKILL.md 1. Fetch the SKILL.md file for the addyosmani-git-workflow-and-versioning skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "addyosmani-git-workflow-and-versioning". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
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.