git-workflow-enforcer

Name: git-workflow-enforcer
Availability: InStock
Author: DYAI

Detect phase and task completions and create Conventional Commits with safety checks.

Updated Feb 14, 2026

Search Tags:#automation #git #workflow #rollback #safety #commits #conventional-commits

Ready to run

npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill git-workflow-enforcer-dyai2025

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow-enforcer
Source: https://github.com/DYAI2025/MOD_shark-engine/tree/main/sharkengine/.claude/skills/git-workflow-enforcer
Command: npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill git-workflow-enforcer-dyai2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures every meaningful change is committed, preventing work loss and enabling granular rollback across phase and task workflows.

Core Features & Use Cases

Auto-detect phase and task completions and trigger a commit
Validate branch safety, merge conflicts, and upstream tracking
Generate Conventional Commits messages and provide rollback commands
Offer feedback on commit success and kicking off automatic validation

Quick Start

Enable the git-workflow-enforcer to automatically detect phase and task changes and generate a Conventional Commits–compliant commit after each milestone.

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 completing development phases?▼

To automate git commits after development phases, you can use a workflow enforcer to detect phase and task completions and automatically generate Conventional Commits. This ensures every meaningful change is committed, preventing work loss and enabling granular rollback.

What is the best way to enforce Conventional Commits in a software workflow?▼

The best way to enforce Conventional Commits in a software workflow is to implement automatic commit message generation triggered by phase and task completions. This guarantees standardized commit history and includes safety checks like branch validation and upstream tracking.

How does automatic rollback work with uncommitted changes in Git?▼

Automatic rollback with uncommitted changes works by detecting phase and task completions, validating branch safety and merge conflicts, and then creating commits with provided rollback commands. This prevents work loss and enables granular rollback across workflows.

Can I validate branch safety and merge conflicts before committing?▼

Yes, you can validate branch safety and merge conflicts before committing by applying safety checks within an automated Git workflow. These validations execute prior to generating Conventional Commits, ensuring upstream tracking and branch integrity before changes are committed.

When do I need automatic commit generation for task workflows?▼

You need automatic commit generation for task workflows when you want to ensure every meaningful change is committed without manual intervention. It is essential for preventing work loss and providing granular rollback capabilities across software development phases.

Does automated Git workflow enforcement handle post-commit feedback?▼

Yes, automated Git workflow enforcement handles post-commit feedback by offering success notifications and kicking off automatic validation. This feedback loop confirms the Conventional Commits execution and ensures the continuous safety of the branch.