Why are PRs created against the develop branch instead of main?

In the Tzurot workflow, main is reserved exclusively for stable releases. All active development and feature PRs must target the develop branch for proper integration and testing.

How does it protect uncommitted work?

The skill implements a Git Safety Protocol that flags high-risk commands like 'git reset --hard' or 'git clean', requiring explicit permission before execution to prevent data loss.

How are version bumps handled across the repository?

It utilizes a specialized 'bump-version' script that automatically synchronizes versioning across all nine package.json files within the Tzurot ecosystem.

What is the primary git strategy used by this skill?

It uses a strict rebase-only strategy. Squash and merge operations are disabled in the repository settings to ensure a clean, linear project history.

Does this skill handle GitHub CLI bugs?

Yes, it includes specific workarounds and direct REST API calls for known issues with the 'gh' command, such as the classic projects deprecation error when editing pull requests.

Tzurot Git Workflow

Name: Tzurot Git Workflow
Author: lbds137

bylbds137

•

Developer Tools

Standardizes the Tzurot v3 development lifecycle through rebase-only strategies, PR management, and safety-first git operations.

About

The Tzurot Git Workflow skill equips Claude with the specific protocols required for the Tzurot project, ensuring a clean, linear history through a strict rebase-only workflow. It automates branch creation, enforces standardized commit messages with AI attribution, and prevents accidental data loss with built-in safety protocols. By targeting the develop branch for all feature PRs and providing workarounds for GitHub CLI limitations, this skill streamlines the contribution process while maintaining high code quality and consistency across the repository's multiple packages.

Key Features

Provides tested workarounds for known GitHub CLI (gh) limitations and REST API overrides.
Automates standardized commit messages with required AI co-author attribution.
7 GitHub stars
Implements safety protocols to prevent accidental deletion or overwriting of uncommitted work.
Manages complex release cycles including multi-package version bumping across 9 files.
Enforces a strict rebase-only workflow to maintain a clean linear commit history.

Use Cases

Safely performing rebases and resolving conflicts without risking loss of local changes.
Executing multi-package version bumps and release PRs to the main branch.
Managing feature branch lifecycles from creation to PR submission against the develop branch.

About

Key Features

Provides tested workarounds for known GitHub CLI (gh) limitations and REST API overrides.
Automates standardized commit messages with required AI co-author attribution.
7 GitHub stars
Implements safety protocols to prevent accidental deletion or overwriting of uncommitted work.
Manages complex release cycles including multi-package version bumping across 9 files.
Enforces a strict rebase-only workflow to maintain a clean linear commit history.

Use Cases

Safely performing rebases and resolving conflicts without risking loss of local changes.
Executing multi-package version bumps and release PRs to the main branch.
Managing feature branch lifecycles from creation to PR submission against the develop branch.