git-workflow-and-versioning
#7 in Git & Code ManagementStructures git workflow practices.
Overview
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, 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. Use when asked to write a commit message or a changelog entry for a change, or to split a change into commits, even when the diff is pasted inline and the message seems easy to write from it.From the project's GitHub description
Our editorial assessment of git-workflow-and-versioning is still in review. Facts below come from the repository and our catalogue.
Technical specifications
Each attribute is labelled with where it came from.
Install
A skill is a set of instructions your agent loads. Install it into the agent you use; there is nothing to host.
$ npx skills add https://github.com/addyosmani/agent-skills --skill git-workflow-and-versioningAlternatives
Also in Git & Code Management
Same category, not necessarily equivalent.
git-guardrails-claude-code
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
caveman-commit
Write a Conventional Commits message compressed to intent only.
Reviews
Community ratings are kept separate from Beav Scout rankings.
No reviews yet. Community reviews and comments are opening soon; you'll be able to rate git-workflow-and-versioning once signed in.