tzurot-git-workflow

Enforce a rebase-only Git workflow with pre-push tests and PRs to develop.

7|2|Updated May 17, 2025
One-click install
npx skills add https://github.com/lbds137/tzurot --skill tzurot-git-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tzurot-git-workflow
Source: https://github.com/lbds137/tzurot/tree/main/.claude/skills/tzurot-git-workflow
Command: npx skills add https://github.com/lbds137/tzurot --skill tzurot-git-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining a clean, linear Git history and preventing merge conflicts in a collaborative (even with AI) project requires a strict workflow. This Skill outlines the rebase-only strategy for Tzurot v3, ensuring a clear and manageable codebase.

Core Features & Use Cases

  • Rebase-Only Enforcement: Understand and follow the project's strict rebase-only policy for a clean, linear Git history.
  • PR Workflow: Create pull requests targeting develop, ensuring proper review and integration into the main development branch.
  • Commit Message Format: Adhere to conventional commit messages for clear, automated changelogs and improved traceability.
  • Pre-Push Safety Checks: Mandatorily run tests, linting, and type checks before every push to prevent breaking changes and maintain code quality.

Quick Start

Use the tzurot-git-workflow skill to create a new feature branch from develop, make a commit with a conventional message, and then rebase onto the latest develop before pushing.

Frequently Asked Questions about tzurot-git-workflow

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

FAQPage Schema
How do I enforce a rebase-only Git workflow in my project?

A rebase-only workflow maintains a clean, linear Git history by rebasing feature branches onto the latest develop instead of merging. This Skill enforces that strategy for Tzurot v3 projects, requiring commits to be rebased before pushing and PRs to target develop exclusively, preventing merge commits and ensuring auditable history.

What's the correct way to write commit messages for CI/CD automation?

Conventional commit messages follow a structured format that enables automated changelog generation and improves traceability. This Skill requires adherence to that standard so your commits integrate cleanly with CI/CD pipelines and version control automation in Tzurot v3 projects.

How do I prevent breaking changes before pushing to version control?

Pre-push safety checks run tests, linting, and type checks automatically before commits reach the remote repository. This Skill mandates those checks in your workflow to catch failures early and maintain code quality across pull requests targeting develop.

Can I use a rebase workflow with pull requests?

Yes. This Skill integrates rebase-only enforcement with PR workflows by requiring feature branches to rebase onto develop before opening a pull request. PRs remain the review mechanism while the rebase strategy keeps history linear and conflict-free.

What happens when I need to resolve conflicts during a rebase?

Rebase conflicts occur when changes on develop conflict with your feature branch. This Skill documents the process for resolving those conflicts and completing the rebase safely within Tzurot v3 projects, ensuring you can recover and push without merge commits.