1. OUTPUT START MESSAGE:

🎯 STARTING: Commit Creator
Type: {type}
Message: {message}
Work ID: {work_id or "none"}
Author Context: {author_context or "none"}
───────────────────────────────────────

2. LOAD CONFIGURATION:

Load repo configuration to determine:

• Active handler platform (github|gitlab|bitbucket)
• Commit format preference (conventional|faber)
• Signing requirements
• Default author information

Use repo-common skill to load configuration.

3. VALIDATE INPUTS:

Message Validation:

• Check message is non-empty
• Validate message length (summary < 72 chars)
• Ensure no newlines in summary

Type Validation:

• Verify type is valid conventional commit type
• Check type matches allowed types list
• Validate scope format if provided

Work ID Validation (if provided):

• If work_id is provided, validate work_id format
• Ensure work_id is traceable
• work_id is optional

Author Context Validation:

• If provided, verify valid FABER context
• Check: architect|implementor|tester|reviewer
• Optional but recommended for FABER workflows

4. FORMAT COMMIT MESSAGE:

Create properly formatted commit message following Conventional Commits + FABER metadata:

<type>[optional scope]: <description>

[optional body]

Work-Item: #{work_id}  (if provided)
Author-Context: {author_context}  (if provided)
Phase: {current_phase}  (if provided)

[optional footer(s)]

Example Formatted Message:

feat(export): Add CSV export functionality

Implements user data export to CSV format with configurable columns and
filtering options. Includes comprehensive error handling and progress reporting.

Work-Item: #123
Author-Context: implementor
Phase: build

Closes #123

5. CHECK FOR CHANGES (Self-Contained Idempotency):

Before creating commit, check if there are changes to commit:

1. Run: git status --porcelain
2. Check for staged or unstaged changes

If NO changes to commit (clean working directory):
   - Return early with SUCCESS status (not error!)
   - Message: "No changes to commit - working directory is clean"
   - This is EXPECTED in resume/retry scenarios
   - Skip all subsequent steps (self-contained behavior)

If changes exist but none are staged:
   - Stage all changes: git add .
   - Continue with commit creation

This self-contained check ensures:

• The step is idempotent (safe to call multiple times)
• Workflow orchestrators don't need conditional logic
• Resume/retry scenarios work correctly (no error when nothing to commit)
• Clean working directory is a valid success state

Note: The allow_empty parameter is now only needed for intentional empty commits (e.g., marking a point in history). Normal "nothing to commit" returns success.

6. INVOKE HANDLER:

Invoke the active source control handler skill to create the commit.

Determine Handler: Read the platform from config at config.handlers.source_control.active (e.g., "github", "gitlab", "bitbucket").

Construct Handler Skill Name: fractary-repo:handler-source-control-{platform}

• For GitHub: fractary-repo:handler-source-control-github
• For GitLab: fractary-repo:handler-source-control-gitlab
• For Bitbucket: fractary-repo:handler-source-control-bitbucket

Invoke the Handler: Use the Skill tool with the handler skill name:

Skill(skill="fractary-repo:handler-source-control-github")

IMPORTANT: Before invoking the handler, output the operation request as JSON so the handler can parse it:

{
  "operation": "create-commit",
  "parameters": {
    "message": "<formatted_message>",
    "type": "<type>",
    "work_id": "<work_id or empty string>",
    "author_context": "<author_context or empty string>",
    "description": "<description or empty string>"
  }
}

The handler skill will:

• Read the JSON operation request from the conversation context
• Execute the appropriate platform-specific script (scripts/create-commit.sh)
• Return JSON with status, commit_sha, and message

7. VALIDATE RESPONSE:

• Check handler returned success status
• Verify commit SHA is valid
• Confirm commit exists in Git history
• Validate commit message was applied correctly

8. OUTPUT COMPLETION MESSAGE:

✅ COMPLETED: Commit Creator
Type: {type}
Commit SHA: {commit_sha}
Work Item: {work_id or "none"}
Message: {message}
───────────────────────────────────────
Next: Run /fractary-repo:push to push changes when ready