git-workflow

Standardize Git branching and worktree practices across agent workflows.

1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/minhcopilot/antigravity --skill git-workflow-minhcopilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/minhcopilot/antigravity/tree/main/skills/git-workflow
Command: npx skills add https://github.com/minhcopilot/antigravity --skill git-workflow-minhcopilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enforces consistent Git practices across agent workflows, promoting isolated environments with worktrees and a clean, repeatable lifecycle for features and PRs.

Core Features & Use Cases

  • Standard Branch Setup: Clear guidance for creating and naming feature branches and integrating with the main branch.
  • Isolated Worktrees (RECOMMENDED): Enable parallel development without polluting the current workspace and simplify PR reviews.
  • Branch Lifecycle Closure: Mandatory steps for merging, abandoning, or cleaning up branches to prevent drift.
  • Instrumentation: Optional logging to observe workflow usage and diagnose issues.

Quick Start

Clone the repository containing this skill and review its guidance. Use the recommended commands to start a new feature, such as switching to main, pulling latest changes, and creating a feature branch, or invoke the provided worktree scripts for isolated work environments. Example commands: git checkout main; git pull origin main; git checkout -b feature/{name}.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I use git worktrees for parallel feature development?

Git worktrees enable parallel development by creating isolated workspaces without polluting your current directory, allowing you to manage multiple feature branches simultaneously and simplify PR reviews.

What is the standard lifecycle for managing feature branches?

Standard branch lifecycle management requires mandatory steps for creating, merging, abandoning, or cleaning up feature branches to prevent drift and ensure consistent closure across complex projects.

How do I set up a standard branching workflow for a new feature?

To set up a standard branching workflow, switch to the main branch, pull the latest changes, and create a new feature branch using commands like git checkout main, git pull origin main, and git checkout -b feature/{name}.

Can I track git workflow usage and diagnose issues?

Yes, optional instrumentation allows you to observe git workflow usage and diagnose issues by logging actions taken during branch setup, feature development, and lifecycle closure.

When should I use isolated worktrees instead of standard branching?

Use isolated worktrees when working on complex projects requiring parallel development across multiple features, preventing workspace pollution and ensuring clean environments for PR reviews.

Why do I need mandatory branch lifecycle closure steps?

Mandatory branch lifecycle closure steps are needed to prevent branch drift and maintain repository hygiene by ensuring abandoned or merged feature branches are properly cleaned up.