zenith

Automate git workflows in GitHub monorepos with safety checks.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/kpatel513/zenith --skill zenith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zenith
Source: https://github.com/kpatel513/zenith/tree/main
Command: npx skills add https://github.com/kpatel513/zenith --skill zenith

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Zenith helps teams safely automate Git workflows in large shared repos, reducing risk of wrong commits and unsafe operations.

Core Features & Use Cases

  • Detects repository state and contamination before actions
  • Manages feature branches, stacked PRs, and PR updates across monorepos
  • Provides deterministic push/sync flows with safety prompts and rollbacks when needed

Quick Start

Type /zenith in Claude Code to begin automating your git workflow.

Frequently Asked Questions about zenith

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

FAQPage Schema
How do I automate safe git workflows in a GitHub monorepo?

You can automate git workflows in a GitHub monorepo by applying diagnostics-first state checks, non-destructive prompts, and cross-folder contamination detection before branching, committing, or pushing. This ensures safe operations and clear next-step guidance without external services.

Can I manage stacked PRs across different folders in a monorepo?

Stacked PRs across monorepo folders are managed by detecting repository state and cross-folder contamination before actions, enabling deterministic push, sync, and PR update flows with safety prompts and rollbacks to prevent unsafe operations.

What is cross-folder contamination detection in monorepo git workflows?

Cross-folder contamination detection in monorepo git workflows identifies unintended changes across different project folders before branching or committing, ensuring that feature branches remain isolated and reducing the risk of wrong commits in shared repositories.

Does this git workflow automation require external services or CI pipelines to run?

No external services are required. All git workflow operations, including branching, syncing, pushing, and PR management via git and gh, run locally using the repository's configuration to tailor behavior and enforce safety checks.

How do I handle conflict resolution when syncing branches in a multi-team monorepo?

Conflict resolution when syncing branches in a multi-team monorepo is handled through deterministic sync flows that enforce diagnostics-first state checks, explicit confirmations for destructive actions, and clear next-step guidance to safely resolve conflicts and update PRs.

When should I use automated git workflow safety checks for monorepo development?

Automated git workflow safety checks should be used when teams work on shared ML or multi-team monorepos where safe branching, stacked PRs, per-repo configurations, and non-destructive operations are critical to preventing wrong commits and unsafe state transitions.