How do I install the Execution Git Workflow skill?

Run npx skillmds@latest add deankelly751/execution-git-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Execution Git Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Execution Git Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Execution Git Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Execution Git Workflow?

DeanKelly751 (@deankelly751) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Execution Git Workflow by deankelly751

Name: Execution Git Workflow
Author: DeanKelly751

Execution Git Workflow

Git branching strategy, PR workflow, commit conventions, and release process. Decision framework for choosing a workflow. Use when establishing team Git conventions, designing branch protection rules, or reviewing Git practices.

DeanKelly751 Updated Sep 21, 2026

File contents

Git Workflow

Purpose

Choose and implement a Git workflow appropriate for team size and release cadence.

Workflow Selection

Workflow	Best for	Release cadence
Trunk-based	Small teams, CD, feature flags	Continuous
GitHub Flow	Most teams, simple branching	On merge to main
Git Flow	Strict release schedules, multiple versions	Scheduled releases

Default recommendation: Trunk-based with short-lived branches (< 2 days).

Branch Convention

main — always deployable, protected
feature/description — short-lived work branches
fix/description — bug fix branches
release/vX.Y.Z — only if using Git Flow

Commit Message Convention

Format: type(scope): description

Types: feat, fix, refactor, docs, test, chore, perf, ci

Examples:

feat(auth): add OAuth2 login flow
fix(api): handle null response from payment provider
refactor(orders): extract validation to dedicated service

Pull Request Workflow

Create branch from main (keep it short-lived)
Push early and often (enables CI feedback)
Open PR when ready for review (or draft PR for early feedback)
CI must pass before review
At least one approval required
Squash merge to main (clean history)
Delete branch after merge

Branch Protection Rules

Require CI to pass before merge
Require at least 1 approval
Dismiss stale approvals on new push
No direct push to main
Linear history (squash or rebase merges)

Related Skills

deployment/execution-cicd-pipeline — pipeline triggered by Git events
deployment/knowledge-cicd-principles — CI requires frequent integration

---name: execution-git-workflowdescription: Git branching strategy, PR workflow, commit conventions, and release process. Decision framework for choosing a workflow. Use when establishing team Git conventions, designing branch protection rules, or reviewing Git practices.---# Git Workflow## PurposeChoose and implement a Git workflow appropriate for team size and release cadence.## Workflow Selection| Workflow | Best for | Release cadence ||----------|----------|-----------------|| Trunk-based | Small teams, CD, feature flags | Continuous || GitHub Flow | Most teams, simple branching | On merge to main || Git Flow | Strict release schedules, multiple versions | Scheduled releases |**Default recommendation**: Trunk-based with short-lived branches (< 2 days).## Branch Convention- `main` — always deployable, protected- `feature/description` — short-lived work branches- `fix/description` — bug fix branches- `release/vX.Y.Z` — only if using Git Flow## Commit Message ConventionFormat: `type(scope): description`Types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `perf`, `ci`Examples:- `feat(auth): add OAuth2 login flow`- `fix(api): handle null response from payment provider`- `refactor(orders): extract validation to dedicated service`## Pull Request Workflow1. Create branch from main (keep it short-lived)2. Push early and often (enables CI feedback)3. Open PR when ready for review (or draft PR for early feedback)4. CI must pass before review5. At least one approval required6. Squash merge to main (clean history)7. Delete branch after merge## Branch Protection Rules- [ ] Require CI to pass before merge- [ ] Require at least 1 approval- [ ] Dismiss stale approvals on new push- [ ] No direct push to main- [ ] Linear history (squash or rebase merges)## Related Skills- `deployment/execution-cicd-pipeline` — pipeline triggered by Git events- `deployment/knowledge-cicd-principles` — CI requires frequent integration

Frequently asked questions