commit-orchestrator

Enforce feature-branch workflows and conventional commit messages for protected branches.

Updated Nov 24, 2025

Search Tags:#automation #git #workflow #branch-management #conventional-commits #feature-branch #crash-resilience

Ready to run

npx skills add https://github.com/greentcsolutions-lab/tc-helper-app --skill commit-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-orchestrator
Source: https://github.com/greentcsolutions-lab/tc-helper-app/tree/main/.claude/skills/commit-orchestrator
Command: npx skills add https://github.com/greentcsolutions-lab/tc-helper-app --skill commit-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents direct commits to protected branches by enforcing feature-branch workflows and conventional commit messages, ensuring safe collaboration and a verifiable history. It also provides crash-resilience by tracking the current work state with a .claude-branch file so you can resume after restarts.

Core Features & Use Cases

Enforces safe git flow: never commit to main, always use a feature branch named with a conventional pattern, and prompt for push approval.
Maintains crash-resilience via .claude-branch persistence to resume interrupted sessions.
Guides automated workflows for Next.js + TypeScript projects, reducing human error in release processes.

Quick Start

Start a new feature-branch workflow for your task and let the orchestrator guide the commit process.

Frequently Asked Questions about commit-orchestrator

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

FAQPage Schema

How do I prevent direct commits to main and enforce a feature-branch workflow?▼

To prevent direct commits to protected branches, you can use a guard that blocks pushes to main and requires conventionally named feature branches. This Skill enforces such safe git flow and manages staged changes to ensure verifiable history.

How do I enforce conventional commit messages in automated git workflows?▼

Enforcing conventional commit messages in automated git workflows is handled by guiding the commit process with strict branch management and staged changes. This ensures all commits adhere to conventional patterns before being pushed.

Can I resume a git workflow session after a crash or restart?▼

Yes, you can resume a git workflow session after a crash or restart. This Skill tracks your current work state using a .claude-branch persistence file, enabling crash-resilience and seamless recovery of interrupted collaborative sessions.

Does this git flow orchestrator work with Next.js and TypeScript projects?▼

Yes, this git flow orchestrator works with Next.js and TypeScript projects. It is specifically designed to guide automated workflows for these collaborative environments, reducing human error in release processes.

What is the best way to manage feature branches and push approvals in automated workflows?▼

The best way to manage feature branches and push approvals in automated workflows is using an orchestrator that enforces conventional branch naming and prompts for approval before pushing. This approach guarantees safe collaboration and verifiable git history.

Why does my automated git workflow need staged changes and approvals?▼

Your automated git workflow needs staged changes and approvals to guide git operations safely and reduce human error. Implementing strict branch management ensures only verified, conventionally committed changes reach protected branches.