workflow-config-system

name	Workflow Config System
description	The agent implements a centralized workflow configuration system for Git workflows, enabling set-once-use-everywhere automation for trunk-based development, gitflow, and github-flow patterns with integrated testing automation.
category	devops
related_skills	["devops/git-hooks","devops/feature-flags","devops/github-actions","methodology/finishing-development-branch","methodology/test-task-generation","methodology/test-enforcement"]
related_commands	["/workflow:init","/workflow:trunk-based","/workflow:status","/git:commit","/git:pr","/quality:verify-done","/quality:coverage-check","/dev:feature-tested"]

Workflow Config System

Overview

The Workflow Config System provides a centralized configuration file (.omgkit/workflow.yaml) that defines Git workflow preferences, commit conventions, PR templates, code review settings, deployment configuration, and git hooks. Once configured, all OMGKIT commands automatically respect these settings.

Core Principles

Set Once, Use Everywhere

• Configure workflow preferences in one file
• All commands automatically read and apply settings
• No need to repeat parameters on every command

Convention Over Configuration

• Sensible defaults for all settings
• Only override what you need to customize
• Progressive disclosure of advanced options

Workflow Flexibility

• Support for trunk-based, gitflow, and github-flow
• Easy switching between workflows
• Project-specific customization

Configuration File Location

project-root/
├── .omgkit/
│   └── workflow.yaml    # Main configuration file
├── .git/
│   └── hooks/           # Auto-generated hooks
└── src/

Complete Configuration Schema

# .omgkit/workflow.yaml
# OMGKIT Workflow Configuration
# Version: 1.0

version: "1.0"

# =============================================================================
# GIT WORKFLOW SETTINGS
# =============================================================================
git:
  # Workflow type: trunk-based | gitflow | github-flow
  workflow: trunk-based

  # Main branch name
  main_branch: main

  # Development branch (only for gitflow)
  develop_branch: develop

  # Branch naming prefixes
  branch_prefix:
    feature: "feature/"
    fix: "fix/"
    hotfix: "hotfix/"
    release: "release/"
    chore: "chore/"

  # Maximum age for feature branches (trunk-based)
  max_branch_age_days: 2

  # Auto-delete branch after merge
  delete_branch_on_merge: true

  # Require linear history (rebase before merge)
  linear_history: true

# =============================================================================
# COMMIT SETTINGS
# =============================================================================
commit:
  # Use conventional commits format
  conventional: 

  
   

  
  
           
            
           
          
       
           
           
          
             
          

  
   

  
   
   

  
   
   





  
  
   

  
   

  
   

  
   

  
   []

  
   

  
   

  
  
     
    
    
       [, ]
       [, ]
       [, ]
       []
       []
       []
    
    
       []
       []
       [, ]
       []

  
   
     





  
   

  
     

  
  
                
             
          
                   
           
           

  
   

  
   

  
  
     
     
     
     

  
  
     
     
     
     





  
   

  
   

  
   

  
   

  
   []

  
  
     
     
     

  
  
     
     





  
  
     
    
                  
            
                
         

  
  
     
     
     

  
  
     
    
                  
         
        

  
  
     
    
               
               





  
   

  
   

  
     

  
   





  
  
     

  
   

  
  
    
               
                
             
    
       
       
    
       
       
    
       
       

  
  
     
     

  
  
     
     
     
     

  
  
     
     
     

  
  
     
     
     





  
   

  
  
     
     
     
       

  
   

Workflow Types

Trunk-Based Development

Best for: Teams practicing continuous deployment, small PRs, feature flags.

git:
  workflow: trunk-based
  main_branch: main
  max_branch_age_days: 2
  delete_branch_on_merge: true

feature_flags:
  provider: vercel-edge
  require_for_wip: true

Characteristics:

• Single main branch
• Short-lived feature branches (< 2 days)
• Feature flags for incomplete work
• Continuous deployment to production
• Small, frequent commits

GitHub Flow

Best for: Teams with regular releases, code review focus.

git:
  workflow: github-flow
  main_branch: main
  max_branch_age_days: 7
  delete_branch_on_merge: true

Characteristics:

• Main branch always deployable
• Feature branches for all changes
• PR-based code review
• Deploy after merge

GitFlow

Best for: Teams with scheduled releases, multiple environments.

git:
  workflow: gitflow
  main_branch: main
  develop_branch: develop
  branch_prefix:
    feature: "feature/"
    release: "release/"
    hotfix: "hotfix/"

Characteristics:

• Main and develop branches
• Feature branches from develop
• Release branches for staging
• Hotfix branches for urgent fixes

Command Integration

How Commands Use Config

All OMGKIT git commands automatically read from .omgkit/workflow.yaml:

# /git:commit reads commit settings
git:
  commit:
    conventional: true
    allowed_types: [feat, fix, ...]

# /git:pr reads PR settings
git:
  pr:
    template: auto
    require_review: true
    labels: ...

# /dev:review reads review settings
git:
  review:
    auto_review: true
    checks: [security, performance, ...]

Config Precedence

1. Command-line arguments (highest priority)
2. .omgkit/workflow.yaml settings
3. Default values (lowest priority)

Initialization

Quick Start

# Initialize with interactive setup
/workflow:init

# Initialize with specific workflow
/workflow:init --workflow=trunk-based

# Initialize with all defaults
/workflow:init --defaults

Manual Setup

Create .omgkit/workflow.yaml manually:

version: "1.0"

git:
  workflow: trunk-based
  main_branch: main

commit:
  conventional: true

pr:
  require_review: true

review:
  auto_review: true

Validation

The config is validated on every command:

# Check config validity
/workflow:status

# Output:
# Workflow Config Status
# ----------------------
# File: .omgkit/workflow.yaml
# Valid: Yes
# Workflow: trunk-based
# Main Branch: main
# Hooks: pre-commit, commit-msg, pre-push
# Review: auto (security, performance, best-practices)

Best Practices

For Trunk-Based Development

1. Keep branches short-lived

   git:
     max_branch_age_days: 2
   

2. Enable feature flags

   feature_flags:
     provider: vercel-edge
     require_for_wip: true
   

3. Auto-review on PR

   review:
     auto_review: true
     trigger: on_pr
   

4. Squash merges

   pr:
     squash_merge: true
   

For Team Collaboration

1. Enforce conventional commits

   commit:
     conventional: true
     require_scope: true
   

2. Require reviews

   pr:
     require_review: true
     min_reviewers: 2
   

3. Block on critical issues

   review:
     block_on_critical: true
   

For CI/CD

1. Required checks

   ci:
     required_checks:
       - build
       - test
       - lint
   

2. Pre-deploy validation

   deploy:
     pre_deploy_checks:
       - test
       - build
   

Migration Guide

From No Config

1. Run /workflow:init
2. Review generated config
3. Commit .omgkit/workflow.yaml
4. Team syncs and starts using

From .github/workflows

Keep existing workflows, add OMGKIT config for local development:

# .omgkit/workflow.yaml complements .github/workflows
ci:
  provider: github-actions
  # Existing workflows continue to work

Troubleshooting

Config Not Found

Warning: No workflow config found at .omgkit/workflow.yaml
Using default settings. Run /workflow:init to create config.

Invalid Config

Error: Invalid workflow config
- git.workflow must be one of: trunk-based, gitflow, github-flow
- commit.max_subject_length must be a number
Run /workflow:status for details.

Hook Not Running

1. Check hooks are enabled in config
2. Run /hooks:setup to regenerate hooks
3. Verify .git/hooks/ permissions

Related Skills

• devops/git-hooks - Git hooks setup and management
• devops/feature-flags - Feature flag implementation
• devops/github-actions - CI/CD workflows
• methodology/finishing-development-branch - Branch completion patterns