/commit

User Request (/commit --issue #XXXX [message or --auto])
    |
    v
PHASE 0: GITLAB ISSUE VALIDATION (mandatory)
    |-- Parse issue reference
    |-- Validate format (#XXXX)
    |-- Query GitLab API
    |-- BLOCK if invalid
    |
PHASE 1: CHANGE ANALYSIS
    |-- git status (untracked files)
    |-- git diff (staged/unstaged)
    |-- git log (recent commit style)
    |
PHASE 2: MESSAGE GENERATION (if --auto)
    |-- Analyze staged changes
    |-- Determine commit type
    |-- Identify scope
    |-- Draft message with issue footer
    |
PHASE 3: QUALITY VALIDATION
    |-- Pre-commit hooks
    |-- Compilation check
    |-- Test execution
    |-- Quality gates
    |-- Secret scanning
    |
PHASE 4: COMMIT EXECUTION
    |-- Stage relevant files
    |-- Create commit with message
    |-- Add co-author footer
    |-- Verify success
    |
PHASE 5: GITLAB SYNC (automatic)
    |-- Update issue with commit reference
    |-- Update issue status
    |-- Log sync result

--issue #160
    |
    v
Parse Format Check (#XXXX)
    |
    +-- Valid Format --> GitLab API: GET /issues/{iid}
    |                       |
    |                   +---+---+
    |                   |       |
    |              Issue Exists  404 Not Found
    |              PROCEED       BLOCK
    |
    +-- Invalid Format --> BLOCK

# Auto-generate commit message with issue reference
/commit --issue #160 --auto

# Manual message with issue reference
/commit --issue #247 "feat(storage): add Redis caching layer"

# With explicit type and scope
/commit --issue #350 --type feat --scope storage "add Redis caching layer"

# Quick fix
/commit --issue #123 --type fix "resolve null pointer in auth module"

# Let the agent analyze changes and generate message
/commit --issue #160 --auto

# Output example:
# Analyzing staged changes...
# Detected: 3 new files, 2 modified files
# Scope: prismatic_perimeter
# Type: feat
# Generated: feat(perimeter): add security rating calculation engine
# Proceed? [Y/n]

# BLOCKED - No issue reference
/commit --auto
# ERROR: GitLab issue reference is REQUIRED
# Usage: /commit --issue #XXXX [message or --auto]

# BLOCKED - Invalid issue format
/commit --issue issue-160 --auto
# ERROR: Invalid issue format. Expected #XXXX (e.g., #160, #247)

# BLOCKED - Issue does not exist
/commit --issue #99999 --auto
# ERROR: GitLab issue #99999 does not exist

type(scope): subject

Body explaining the changes in detail.

Closes #XXXX

---
Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

PHASE 0: GITLAB ISSUE VALIDATION
    |-- Parse --issue parameter
    |-- Validate format: must match #[0-9]+
    |-- API call: GET /projects/{id}/issues/{iid}
    |-- BLOCK if 404 or API error
    |-- Warning if issue is closed (non-blocking)
    |
PHASE 1: CHANGE ANALYSIS
    |-- git status: identify untracked and modified files
    |-- git diff: analyze content of changes
    |-- git log: sample recent commit style for consistency
    |
PHASE 2: MESSAGE GENERATION (if --auto)
    |-- Categorize changes by type and scope
    |-- Draft subject line (< 50 chars)
    |-- Generate body with change details
    |-- Append issue reference footer
    |-- Append co-author footer
    |
PHASE 3: QUALITY VALIDATION
    |-- Execute all pre-commit hooks
    |-- Verify zero warnings compilation
    |-- Run test suite for affected modules
    |-- Execute quality gates
    |-- Scan for secrets and credentials
    |-- BLOCK if any check fails
    |
PHASE 4: COMMIT EXECUTION
    |-- Stage specified files (no `git add -A`)
    |-- Create commit with formatted message
    |-- Verify commit success
    |
PHASE 5: GITLAB SYNC
    |-- POST commit reference to GitLab issue
    |-- Update issue labels if applicable
    |-- Log sync result

export GITLAB_TOKEN="glpat-xxxxxxxxxxxxxxxxxxxxx"
export GITLAB_PROJECT_ID="korczis/prismatic-platform"
export GITLAB_ENFORCEMENT_ENABLED="true"

Related Commands