# 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.

- **Type:** Skill
- **Install:** `agentstack add skill-willvelida-code-minions-git-workflow`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [willvelida](https://agentstack.voostack.com/s/willvelida)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [willvelida](https://github.com/willvelida)
- **Source:** https://github.com/willvelida/code-minions/tree/main/packages/git-workflow/skills/git-workflow

## Install

```sh
agentstack add skill-willvelida-code-minions-git-workflow
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 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 |
| Branch complexity | Minimal | Low | High | Medium |
| Code review | Optional | Required | Required | Required |
| Best for | Small teams, simple projects | Most teams | Versioned releases | Open source, external contributors |

## Capabilities

| Capability | Action | Description |
|------------|--------|-------------|
| Initialize Repository | `actions/initialize-repository.md` | Clone, set up remotes, or fork |
| Create Feature Branch | `actions/create-feature-branch.md` | Create and push a feature branch |
| Commit Changes | `actions/commit-changes.md` | Stage and commit with conventional commits |
| Sync with Upstream | `actions/sync-with-upstream.md` | Pull and rebase to stay current |
| Create Pull Request | `actions/create-pull-request.md` | Open a PR for code review |
| Resolve Merge Conflicts | `actions/resolve-merge-conflicts.md` | Handle conflicts during rebase or merge |
| Merge Pull Request | `actions/merge-pull-request.md` | Merge an approved PR into the target branch |
| Create Release | `actions/create-release.md` | Create release branches and tags (Gitflow) |
| Create Hotfix | `actions/create-hotfix.md` | Create and merge hotfix branches (Gitflow) |

## Standards

| Standard | File | Description |
|----------|------|-------------|
| Branch Naming | `standards/branch-naming.md` | Branch prefix and naming conventions |
| Commit Messages | `standards/commit-messages.md` | Conventional commit format and rules |
| Code Review | `standards/code-review.md` | Review checklist and guidelines |
| Merge Strategy | `standards/merge-strategy.md` | When to rebase vs merge |
| Checklist | `standards/checklist.md` | Consolidated compliance checklist |

## Git Safety Protocol

- NEVER update git config without explicit request
- NEVER run destructive commands (`--force`, `hard reset`) without explicit request
- NEVER skip hooks (`--no-verify`) unless user asks
- NEVER force push to `main`/`master`/`develop`
- If a commit fails due to hooks, fix the issue and create a NEW commit (do not amend)

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [willvelida](https://github.com/willvelida)
- **Source:** [willvelida/code-minions](https://github.com/willvelida/code-minions)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-willvelida-code-minions-git-workflow
- Seller: https://agentstack.voostack.com/s/willvelida
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.