Git Workflow and Versioning sets the git habits an agent follows on every code change. Commits are save points, branches are short-lived sandboxes and history serves as documentation.
The skill covers atomic commits, commit message format, change sizing, git worktrees for parallel agents, structured change summaries, pre-commit checks, git bisect and blame, and a release section on semantic versioning, tags and human-written changelogs.
What You Get
- Rules for atomic commits, messages and change sizing
- A branching and worktree workflow for parallel work
- A pre-commit hygiene routine with a secrets check and git bisect, log and blame commands
- Semantic versioning, tagging and changelog guidance with verification lists
Common Use Cases
- Writing a commit message
- Splitting a large change into commits
- Running several agents in parallel branches
- Choosing a version bump and writing a changelog
What Makes It Unique
The skill pairs commit discipline with a release section that treats the tag as the single source of the version and treats the changelog as a document written for consumers. It also asks for a change summary that names what the agent chose not to touch.
Under The Hood
The SKILL.md loads on any code change. The commands it describes run git for commits, branches, worktrees, bisect, blame, tags and pushes, and the project’s test, lint and type check commands. Pushing a tag reaches the remote. It ships no scripts.