Git Workflow and Versioning

Agentit-owned operational adaptation. The verbatim upstream source is retained at vendor/agent-skills/git-workflow-and-versioning/SKILL.md; provenance and license records remain authoritative for that source.

Use the repository's branching, versioning and review conventions. Agentit's task-router owns development modes and verification cadence. This skill supplies Git safety and handoff practices; it does not authorize commits, pushes, merges, releases or deletion.

Establish the working state

Before changing branches or history, inspect the repository root, current branch, git status --short --branch, staged/unstaged diff and git worktree list --porcelain. Inspect upstream/ahead-behind state when a handoff matters. Identify existing user/concurrent work and your ownership. A dirty tree is work to preserve, not a cleanup error.

Use a work branch from the intended base unless project/session instructions say otherwise. Keep it focused and integrate when verified and authorized; do not force a branch lifetime or merge deadline. Do not switch or rewrite a shared checkout while another worker owns it.

Save coherent milestones

A milestone is a useful review, recovery or handoff point: a completed behavior with its relevant tests/docs, a resolved defect, or an explicitly labelled incomplete checkpoint before interruption. Commit at those points when authorized. Editing a file or passing a trivial check does not require a new commit.