Git Workflow
Execute a complete git workflow for collaborative development. Use when user asks to initialize a repo, create branches, commit changes, sync with upstream, open pull requests, resolve conflicts, merge PRs, create releases, or apply hotfixes. Supports Centralized, Feature Branch, Gitflow, and Forking workflows with conventional commits, branch naming standards, and code review guidelines.
Install
npx skills add willvelida/code-minions --skill git-workflowgit clone --depth 1 https://github.com/willvelida/code-minions.git /tmp/code-minions
mkdir -p ~/.claude/skills
cp -r /tmp/code-minions/packages/git-workflow/skills/git-workflow ~/.claude/skills/git-workflowPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Git Workflow ## Overview A complete git workflow skill covering the full development lifecycle — from repository setup through release. Supports four workflow models based on team size and release cadence. ## Workflow Models ### 1. Centralized Workflow All developers commit directly to `main`. Best for small teams or SVN migrations. - Single branch (`main`) - Pull with rebase to stay linear - Conflict resolution before push ### 2. Feature Branch Workflow All development happens on dedicated branches. Core idea: `main` never contains broken code. - Create a branch per feature or fix - Open a pull request for code review - Merge into `main` after approval ### 3. Gitflow Workflow Strict branching model designed around project releases. Extends Feature Branch with release management. - `main` — production-ready code - `develop` — integration branch for features - `feature/*` — new features branch from `develop` - `release/*` — release preparation branches - `hotfix/*` — urgent fixes branch from `main` ### 4. Forking Workflow Each developer has their own server-side fork. Common in open source. - Fork the upstream repository - Clone your fork locally - Push to your fork, open PRs against upstream ## Workflow Selection Guide | Criteria | Centralized | Feature Branch | Gitflow | Forking | |---|---|---|---|---| | Team size | 1–3 | 2–10 | 5+ | Any (open source) | | Release cadence | Continuous | Continuous | Scheduled | Varies |
Details
- Skill name
git-workflow- Repository
- willvelida/code-minions
- Path
packages/git-workflow/skills/git-workflow/SKILL.md- License
- Apache-2.0
- Repo updated
- 11 June 2026
FAQ
What does the Git Workflow skill do?
Execute a complete git workflow for collaborative development. Use when user asks to initialize a repo, create branches, commit changes, sync with upstream, open pull requests, resolve conflicts, merge PRs, create releases, or apply hotfixes. Supports Centralized, Feature Branch, Gitflow, and Forking workflows with conventional commits, branch naming standards, and code review guidelines.
How do I install the Git Workflow skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add willvelida/code-minions --skill git-workflow. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Git Workflow popular?
It lives in willvelida/code-minions, which has 23 GitHub stars and 2 forks.
Related skills
Creating Agent Skill
23willvelida/code-minions
Create and review Agent Skills that follow the open Agent Skills specification and best practices. Use when a user asks to create a new skill, build skill instructions, generate a SKILL.md file, review an existing skill for compliance, or improve skill quality. Covers skill structure, naming conventions, progressive disclosure, writing effective descriptions, creating actions and standards, and validation.
Creating Agents
23willvelida/code-minions
Create and review agent definition files (agents.md) that give AI coding agents a clear persona, project knowledge, executable commands, code style examples, and explicit boundaries. Use when a user asks to create an agent, define an agent persona, write an agents.md file, set up a custom Copilot agent, review an existing agent definition, or improve agent quality. Covers the six core areas: commands, testing, project structure, code style, git workflow, and boundaries.
Creating Devcontainers
23willvelida/code-minions
Create and review DevContainer configurations that follow organisational standards. Use when a user asks to set up a dev container, configure a development environment, create a devcontainer.json, add lifecycle hooks, review an existing DevContainer for compliance, or improve container security. Covers base images, features, extensions, lifecycle hooks, and security hardening.
Merge
40ArogyaReddy/alirezarezvani-claude-skills
Merge the winning agent's branch into base, archive losers, and clean up worktrees.
Git Commit Helper
43lifangda/claude-plugins
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
Raise Pull Requests
23willvelida/code-minions
Raise high-quality pull requests that are easy to review, provide clear context, and follow team conventions. Use when a user asks to open, write, prepare, or submit a pull request. Covers PR sizing, self-review, writing descriptions, submitting PRs, responding to review feedback, and reviewing others' PRs. Follows GitHub best practices for collaboration and code review.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.