skills.rest
salavender
salavenderCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Automate standardized Git branching, worktrees, and lifecycle closure across agents.

47|7|Updated Dec 21, 2025
Search Tags:#automation#git#workflow#collaboration#worktrees#branching#lifecycle
One-click install
npx skills add https://github.com/salavender/antigravity-compound-engineering-plugin --skill git-workflow-salavender
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/salavender/antigravity-compound-engineering-plugin/tree/main/skills/git-workflow
Command: npx skills add https://github.com/salavender/antigravity-compound-engineering-plugin --skill git-workflow-salavender

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures consistent Git practices across all agent workflows, prioritizing isolated work environments via worktrees and enforcing a clean lifecycle closure.

Core Features & Use Cases

  • Standardized Git branching patterns and mandatory lifecycle closure across agents.
  • Option A: Standard Branching and Option B: Isolated Worktree (RECOMMENDED) to keep the main workspace clean.
  • Branch Lifecycle Closure (MANDATORY) with clear steps for merged, local-only, abandoned, WIP, and worktree cleanup scenarios.
  • Instrumentation through a dedicated logging script to track skill usage and workflow events.

Quick Start

Use this skill to standardize Git branching, worktrees, and mandatory lifecycle steps across your development workflows.

Frequently Asked Questions about git-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Git branching patterns across multiple development agents?▼

You can standardize Git branching across agents by applying automated workflow rules that enforce consistent branch creation, worktree isolation, and strict lifecycle closure for feature development and PR reviews.

What is the best way to isolate feature development work without cluttering the main workspace?▼

Using isolated Git worktrees is the best way to keep the main workspace clean. This approach creates separate working directories for each feature branch, preventing file conflicts during multi-agent collaboration.

How do I manage the branch lifecycle closure process after a merge or abandonment?▼

Branch lifecycle closure is managed through mandatory cleanup steps that address merged, local-only, abandoned, and WIP branches. This structured process ensures stale worktrees and branches are systematically removed.

Does Git workflow automation support multi-agent development tasks requiring isolated environments?▼

Yes, Git workflow automation explicitly supports multi-agent development tasks. It provides isolated work environments and enforces strict lifecycle closure to coordinate complex collaboration without workspace conflicts.

Why do I need mandatory lifecycle steps for Git worktrees and branches?▼

Mandatory lifecycle steps are needed to prevent repository clutter from accumulating abandoned branches or worktrees. Enforcing these closure rules maintains a clean workspace and ensures consistent branch hygiene across all agents.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
jimmymalhanjimmymalhan
1

rebase-manager

Rebase dependent pull request branches onto main after a base PR merges.

Community
Intermediate
zizzfizzixzizzfizzix

code-review

Automate code review for architectural, security, and quality compliance.

Community
Advanced
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

using-git-worktrees

Creates an isolated Git worktree workspace for feature development.

Community
Advanced