git-ops

Automate Git worktree creation, commits, and branch finalization workflows.

1|1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/ssimhan/meal-planner --skill git-ops-ssimhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-ops
Source: https://github.com/ssimhan/meal-planner/tree/main/skills/git-ops
Command: npx skills add https://github.com/ssimhan/meal-planner --skill git-ops-ssimhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines advanced Git workflows by managing worktrees, safe branching, and clean finalization, reducing manual setup and potential errors.

Core Features & Use Cases

  • Worktree isolation: Easily create isolated workspaces for feature development using Git worktrees.
  • Atomic commits & branching: Enforce clean, small commits and structured branch finalization workflows.
  • Safe cleanup: Remove temporary worktrees and present finalized changes once tests pass.

Quick Start

Initialize a new feature worktree with: git worktree add <path> -b <branch-name>, then run tests and finalize the branch with the recommended workflow commands.

Frequently Asked Questions about git-ops

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

FAQPage Schema
How do I automate Git worktree setup for isolated feature development?▼

Git worktree automation creates isolated workspaces by adding worktrees to a `.worktrees` or `worktrees/` directory and updating `.gitignore`. This ensures predictable branch lifecycles and clean feature development without manual configuration.

What is the best way to manage Git branch finalization and cleanup?▼

Branch finalization involves enforcing atomic commits and running tests before safely removing temporary worktrees. This structured workflow presents finalized changes predictably and eliminates dangling branches in local environments.

Can I use structured Git workflows for feature branches in CI contexts?▼

Structured Git workflows apply to both local and CI contexts needing isolated workspaces. The process enforces worktree discovery, ensures worktrees are ignored via `.gitignore`, and provides phase-based guidance for finalization.

How do you ensure Git worktrees are ignored in version control?▼

Git worktrees are ignored by enforcing updates to `.gitignore` during worktree discovery. The workflow checks for worktrees in `.worktrees` or `worktrees/` directories and ensures they are excluded from tracking.

Why does my Git worktree workflow need phase-based guidance for commits?▼

Phase-based guidance for commits enforces clean, small, and atomic commits while isolating feature work. This structured approach reduces manual setup errors and ensures predictable branch lifecycles throughout finalization.