git-workflow-and-versioning

Structures git commits, branching, and worktree workflows for disciplined version control.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/memasanz/agent-harness --skill git-workflow-and-versioning-memasanz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/memasanz/agent-harness/tree/main/.github/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/memasanz/agent-harness --skill git-workflow-and-versioning-memasanz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers generating code at high speed often produce giant unreviewable commits, vague messages, and diverging long-lived branches. This Skill enforces disciplined version control so every change stays reviewable, revertable, and traceable. ## Core Features & Use Cases - Atomic Commit Discipline: Enforces small, single-purpose commits (~100 lines) with conventional message types (feat, fix, refactor, test, docs, chore) that explain the why. - Trunk-Based Branching Strategy: Guides short-lived feature branches merged within 1-3 days, with naming conventions and feature-flag alternatives to long-lived branches. - Parallel Work with Worktrees: Shows how to use git worktrees so multiple agents work on separate branches simultaneously without interference. - Use Case: An AI agent implements a feature across several slices, committing each verified increment with a descriptive message, so a broken change can be reverted instantly via the save point pattern. ## Quick Start Ask the agent to commit the current changes following atomic commit conventions with a descriptive conventional-commit message.

Frequently Asked Questions about git-workflow-and-versioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What files should never be committed to git?

Never commit .env files, build output like dist/ or .next/, node_modules/, or *.pem keys. Set up a .gitignore immediately and scan staged diffs for passwords, secrets, API keys, and tokens before committing.