spec-kitty-git-workflow

Define git workflow responsibilities between Python automation and LLM agents.

Updated May 13, 2026
One-click install
npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-git-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kitty-git-workflow
Source: https://github.com/kimprobably/maestro-os/tree/main/.claude/skills/spec-kitty-git-workflow
Command: npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-git-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents workflow breakage by clarifying which git actions Spec Kitty’s Python automation performs versus which actions LLM agents must perform manually, including worktree lifecycle, auto-commit behavior, and the safe-commit pattern.

Core Features & Use Cases

  • Worktree lifecycle governance: Ensures agents use Spec Kitty commands to create and reuse lane worktrees instead of manually running git worktree add.
  • Auto-commit boundaries: Explains when planning artifacts and lane transition artifacts are auto-committed by Python (configurable via auto_commit or --no-auto-commit).
  • Safe-commit and merge execution rules: Documents the safe-commit pattern for lane transitions, plus how merges run (including pre-flight validation, cleanup, and conflict handling expectations).
  • Use case: When implementing multiple dependent WPs in the same execution lane, agents follow the correct commit/rebase/merge responsibilities so merges succeed and worktrees are cleaned up without corrupting the main repo.

Quick Start

Use this spec to guide an agent in implementing a WP (e.g., WP01) by committing implementation changes inside the lane worktree, then handling any required rebase conflicts before requesting for review or merge.

Frequently Asked Questions about spec-kitty-git-workflow

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

FAQPage Schema
How do I manage git worktree lifecycle when automating lane transitions?

Git worktree lifecycle management requires using designated automation commands to create and reuse lane worktrees instead of manually running git worktree add, preventing execution lane breakage. This ensures proper worktree cleanup without corrupting the main repository.

When are planning artifacts auto-committed in a git merge workflow?

Planning artifacts and lane transition artifacts are auto-committed by Python automation during git merge workflows, configurable via the auto_commit setting or the --no-auto-commit flag, establishing clear boundaries for safe-commit staging behavior.

What is the safe-commit pattern for lane transitions in git?

The safe-commit pattern for lane transitions defines strict staging behavior rules, clarifying that LLM agents must manually perform commit, rebase, and conflict resolution actions while Python automation handles artifact auto-commits and pre-flight validation.

Why do git merges fail when implementing multiple dependent work packages in the same execution lane?

Git merges fail when agents incorrectly perform worktree creation or miss required rebase conflict resolution before requesting review. Following strict agent-side commit and rebase responsibilities ensures merges succeed and worktrees clean up properly.

Can I manually run git worktree add for lane implementation?

Manually running git worktree add for lane implementation is prohibited; agents must use designated automation commands to create and reuse worktrees. This prevents breaking worktree and commit sequencing during WP implementation and lane transitions.