Verified:GitHub

git-workflow-and-versioning

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

Updated Jul 1, 2026

Search Tags:#git #code review #version control #commit #branching #worktree #trunk-based development

One-click install

npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill git-workflow-and-versioning-raishoemi

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/raishoemi/traffic-sim-v2/tree/main/.github/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill git-workflow-and-versioning-raishoemi

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 tangled branches. This Skill enforces disciplined version control so every change stays reviewable, revertable, and well-documented. ## Core Features & Use Cases - Atomic Commit Discipline: Enforces small, single-purpose commits with conventional message types (feat, fix, refactor, test, docs, chore) that explain the why behind each change. - Trunk-Based Branching Strategy: Guides short-lived feature branches, branch naming conventions, and git worktrees for running parallel AI agent work in isolated directories. - Pre-Commit Hygiene & Debugging: Provides checklists for staged diff review, secret scanning, test execution, and git bisect/blame workflows for tracking down regressions. - Use Case: An AI agent implementing a feature commits each tested increment with a descriptive message, works in a dedicated worktree, and produces a structured change summary listing what was and was not modified. ## Quick Start Use the git-workflow-and-versioning skill to commit my current changes as atomic commits with proper messages.

Frequently Asked Questions about git-workflow-and-versioning

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

FAQPage Schema

When should I not commit generated files?▼

Do not commit build output like dist/, environment files like .env, or IDE settings. Commit generated files only when the project expects them, such as package-lock.json or database migrations, and maintain a proper .gitignore.