git-workflow-and-versioning

Enforces atomic commits, trunk-based branching, and pre-commit hygiene for every code change.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/insightriot/signal --skill git-workflow-and-versioning-insightriot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/insightriot/signal/tree/main/plugin/skills/ship/git-workflow-and-versioning
Command: npx skills add https://github.com/insightriot/signal --skill git-workflow-and-versioning-insightriot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code often lands as giant unreviewable commits with vague messages, mixed concerns, and no safety net when something breaks. This Skill imposes disciplined version control so every change is reviewable, revertible, and documented. ## Core Features & Use Cases - Atomic Commit Discipline: Enforces one logical change per commit (~100 lines), conventional message types (feat, fix, refactor, test, docs, chore), and separation of refactoring from feature work. - Branching & Worktrees: Guides trunk-based development with short-lived feature branches and git worktrees so multiple agents can work in parallel without interference. - Pre-Commit Hygiene & Debugging: Provides a pre-commit checklist (diff review, secret scanning, tests, lint, typecheck) plus git bisect, blame, and log techniques for debugging. - Use Case: An agent implementing a task-creation feature commits each slice separately (endpoint, form, wiring, tests), runs tests before each commit, and uses git reset --hard HEAD to recover instantly when a change breaks the build. ## Quick Start Ask the agent to apply the git workflow skill to commit the current changes as atomic, well-described commits after verifying tests pass.

Frequently Asked Questions about git-workflow-and-versioning

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

FAQPage Schema
How do I write atomic git commits?▼

Make each commit accomplish one logical objective, such as a single endpoint, component, or test suite. Aim for roughly 100 lines per commit, split changes exceeding 1000 lines, and never mix formatting or refactoring with functional changes.

What is the best git branching strategy for small teams?▼

Trunk-based development is recommended: keep main always deployable and merge short-lived feature branches within 1-3 days. Long-lived branches accumulate merge conflicts and hidden costs; use feature flags for incomplete work instead.

How do I use git worktrees for parallel development?▼

Run git worktree add with a target directory and branch name to create separate working directories per branch. Multiple agents can then work simultaneously without branch switching, and failed experiments are removed with git worktree remove.

What should I check before every git commit?▼

Review the staged diff, scan for secrets like passwords or API keys, run tests, lint, and type checking. Automate these checks with git hooks using husky and lint-staged so they run on every commit.

How do I find which commit introduced a bug?▼

Use git bisect: mark the current HEAD as bad and a known-good commit as good, then git checks out midpoints for you to test until the faulty commit is isolated. git blame and git log --grep also help trace changes.