git-workflow
Git Workflow
When to Use
Use this skill when working with git — branching, committing, creating PRs, resolving merge conflicts, and maintaining clean history. Covers conventional commits, branch naming, PR workflow, rebase vs merge, and safety rules.
This skill is designed for AI-assisted ("vibe coding") workflows where an LLM like Claude Code generates most of the code. The patterns here emphasize diff review discipline, selective staging, and atomic commits — critical when you are not typing every line yourself.
Stack-agnostic — applies to frontend, Python, Rust, and any other language.
Safety rule: Never run destructive git commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D) unless the user explicitly requests them. Always confirm before taking actions that are hard to reverse.
Branch Strategy
Branch Naming Convention
More from michaelkeevildown/claude-agents-skills
neo4j-data-models
Neo4j graph data modeling patterns — node/relationship design, fraud detection schemas, and modeling best practices.
27neo4j-cypher
Neo4j Cypher query language reference — patterns, performance, fraud-domain queries, and Neo4j 5+ features.
13neo4j-driver-js
Neo4j JavaScript driver 6.x — connection setup, session management, impersonation security, transaction functions, type handling, and result-to-UI data mapping.
8shadcn-ui
shadcn/ui component library — installation, usage patterns, theming, form integration, and accessibility.
7fastapi
FastAPI — route definitions, dependency injection, Pydantic models, middleware, and async patterns.
6agent-teams
Agent Teams workflow — parallel multi-agent development with stack-aware coordination (build-first for frontend, TDD for Python/Rust), feature doc lifecycle, file ownership, and quality gates.
6