git-workflow-enforcer

Enforce git commits after each phase using Conventional Commits format.

91|10|Updated Oct 4, 2025

Search Tags:#git #workflow #versioning #rollback #conventional-commits

Ready to run

npx skills add https://github.com/marcusgoll/Spec-Flow --skill git-workflow-enforcer-marcusgoll

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow-enforcer
Source: https://github.com/marcusgoll/Spec-Flow/tree/main/.codex/skills/git-workflow-enforcer
Command: npx skills add https://github.com/marcusgoll/Spec-Flow --skill git-workflow-enforcer-marcusgoll

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Enforces git commits after every meaningful change to enable precise rollback and maintain clean history.

Core Features & Use Cases

Automatic commit generation after phase/task completion
Branch safety checks and dry-run rollback hints
Conventional Commits formatting guidance

Quick Start

Detects uncommitted changes and proposes standardized, traceable commits per phase or task.

Frequently Asked Questions about git-workflow-enforcer

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

FAQPage Schema

How do I prevent lost work when making git commits?▼

Enforce commits after every meaningful change to enable precise rollback. This Skill detects uncommitted changes via git status and automatically generates standardized Conventional Commits, ensuring no work is lost and history remains traceable across workflow phases.

What is Conventional Commits formatting and why should I use it?▼

Conventional Commits is a standardized format for commit messages that improves readability and enables automation. This Skill applies Conventional Commits formatting to commits generated after phases and tasks, creating a clean, machine-readable history for rollback and analysis.

How do I detect uncommitted changes and validate branch safety before merging?▼

Detect uncommitted changes using git status and validate branch safety by checking upstream branches and conflict states. This Skill automates these checks across workflow stages, preventing merges with conflicts and gating completion until all changes are committed.

Can I use commit enforcement across different workflow phases?▼

Yes. This Skill enforces commits across all workflow stages—spec, plan, tasks, analyze, optimize, and preview—triggering standardized commits after each phase completes and file changes occur, maintaining consistent history throughout your process.

What happens if I try to complete a task with uncommitted changes?▼

Completion is gated until changes are committed. The Skill detects uncommitted changes, proposes a Conventional Commits message based on context and file changes, and blocks task progression until you commit, preventing incomplete or lost work.

Does this Skill help with rolling back changes safely?▼

Yes. By enforcing commits after every meaningful change and providing dry-run rollback hints, this Skill enables precise rollback to any previous state. Clean commit history with Conventional Commits formatting makes targeted rollbacks straightforward and auditable.