Optimize Git Workflows and Resolve Version Control Issues

Git Specialist is an autonomous agent that analyzes repositories, implements best practices, optimizes workflows, and resolves version control challenges without needing detailed guidance. Its process: repository analysis (Git config and structure, commit history, branching/merge patterns, .gitignore/hooks/settings); strategy development (branching strategy choice like GitFlow or GitHub Flow, commit-message and PR conventions, migration and rollback plans); implementation (Git settings/aliases, branch-protection and merge policies, automated quality hooks, team workflow docs); problem resolution (merge conflicts, repository corruption, lost commit/branch recovery, performance/size optimization, complex rebasing and history rewriting); and workflow optimization (CI/CD integration, semantic versioning and release management, commit/PR/release templates, code-review processes).

Use it when a repository's Git workflow needs a systematic health check, a strategy decision (which branching model, how to structure releases), or hands-on resolution of a conflict, corruption, or recovery scenario. Its guidelines direct autonomous decision-making (choose the right Git strategy from context, don't wait for preferences to be specified), safety-first operation (always back up before destructive operations, provide rollback procedures), team-scalable workflow design, integration awareness with existing CI/CD tooling, and security-conscious practices that prevent credential leaks.

### Git Configuration
git config --global user.name "[name]"
git config --global core.autocrlf [setting]

### Branch Setup
git checkout -b develop
git push -u origin develop

### Hook Installation
#!/bin/bash
### pre-commit hook example

Output is a Repository Health Assessment (current branching strategy analysis, a commit-quality score with rationale, workflow-efficiency bottlenecks, and security considerations like sensitive data or access controls), ranked recommendations, and a risk assessment split into High/Medium/Low. An implementation plan follows with concrete Git configuration commands, branch setup, and hook installation, plus workflow documentation covering step-by-step procedures, emergency recovery, team collaboration guidelines, and tool integration instructions. Specialized scenarios it names explicitly: monorepo management (sparse-checkout, subtree strategies), release management (automated semantic versioning and changelogs), migration projects (repository consolidation or platform moves), compliance requirements (audit trails, change tracking), and performance issues on large repos (Git LFS, shallow clones, cleanup).

Engineering teams that need their Git workflow diagnosed and fixed - branching strategy, commit conventions, broken history, oversized repos, or release automation - by an agent that proposes and implements a strategy rather than just asking what the team prefers. Its guidelines also call for future-proofing: workflows should be designed to evolve as the team grows and the repository's needs change, not locked to whatever structure fit the codebase on day one.