git-workflow-enforcer

Enforce git commits after phases and tasks with Conventional Commits messages.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill git-workflow-enforcer-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow-enforcer
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/git-workflow-enforcer
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill git-workflow-enforcer-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that every meaningful change is committed to enable granular rollback and prevent lost work, eliminating silent progress without a trace.

Core Features & Use Cases

  • Automatic commit enforcement: Triggers commits after phase and task completions to create rollback points.
  • Conventional Commits generation: Automatically formats commit messages according to Conventional Commits standards.
  • Safety checks: Validates branch safety, detects merge conflicts, and verifies upstream tracking before committing.
  • Feedback & rollback: Provides clear feedback with rollback commands and status updates to streamline recovery if needed.

Quick Start

Enable the enforcer to monitor your workflow and start receiving guidance after each phase or task completion. When changes are detected, commit suggestions will be generated, and you will be guided to maintain a clean, auditable history.

Frequently Asked Questions about git-workflow-enforcer

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

FAQPage Schema
How do I automate git commits after every development phase to prevent lost work?

Automating git commits after every phase requires enforcing a disciplined workflow that detects task completions and uncommitted changes. This Skill blocks unsafe progress and auto-generates Conventional Commits messages to create granular rollback points.

What is a conventional commits workflow and how does auto-generation work?

A conventional commits workflow formats commit messages according to standardized prefixes. This Skill auto-generates these formatted messages automatically after detecting phase and task completions, ensuring a clean and auditable git history without manual message formatting.

How do I rollback changes if an automated commit breaks my code?

To rollback changes after a failed automated commit, use the rollback commands provided in the status feedback. The Skill outputs these specific commands alongside concise status updates after performing safety checks and committing changes to enable granular recovery.

Does git commit enforcement work with branches that have merge conflicts or no upstream tracking?

Git commit enforcement does not work with branches that have merge conflicts or lack upstream tracking. The Skill runs safety checks to validate branch safety, detect conflicts, and verify upstream tracking, blocking unsafe progress before committing.

Do I need Bash and Git installed to enforce a Spec-Plan-Implement commit lifecycle?

Yes, you need Bash and Git installed to enforce a Spec-Plan-Implement commit lifecycle. This Skill requires both tools to operate within the lifecycle, detect uncommitted changes, execute safety checks, and auto-generate Conventional Commits.