1. OUTPUT START MESSAGE:

🎯 STARTING: Tag Manager
Operation: {operation}
Tag: {tag_name}
───────────────────────────────────────

2. LOAD CONFIGURATION:

Load repo configuration to determine:

• Active handler platform (github|gitlab|bitbucket)
• GPG signing requirements
• Default remote name
• Tag naming conventions

Use repo-common skill to load configuration.

3A. CREATE TAG WORKFLOW:

Validate Tag Name:

• Check tag_name follows semantic versioning
• Validate format: v[0-9]+.[0-9]+.[0-9]+(-[a-z0-9.-]+)?
• Examples: v1.0.0, v2.1.3, v1.0.0-beta.1, v2.0.0-rc.2
• Reject invalid formats

Check Existing Tags:

if tag exists and not force:
    ERROR: "Tag already exists: {tag_name}. Use force=true to overwrite."

Validate Commit:

• Verify commit_sha exists (or HEAD valid)
• Check commit is reachable in history
• Ensure commit is not invalid/corrupted

Validate Message:

• Check message is non-empty
• Validate message format
• Ensure message provides context for release

Check GPG Configuration: If sign=true or required by config:

• Verify GPG configured: git config user.signingkey
• Test GPG key accessible
• Warn if GPG not available

Invoke Handler:

Use the Skill tool with command fractary-repo:handler-source-control-<platform> where is from config. Pass parameters: {tag_name, message, commit_sha, sign, force}

The handler will:

• Create annotated Git tag
• Apply GPG signature if requested
• Return tag details

3B. PUSH TAG WORKFLOW:

Validate Tag:

• Check tag exists locally
• Verify tag is properly formatted
• Validate tag is annotated (not lightweight)

Check Remote:

• Verify remote exists
• Test remote connectivity
• Check authentication

Handle "all" Special Case: If tag_name="all":

• Push all local tags
• Warn about multiple tag push
• Require confirmation

Invoke Handler:

Use the Skill tool with command fractary-repo:handler-source-control-<platform> where is from config. Pass parameters: {tag_name, remote}

The handler will:

• Push tag(s) to remote
• Verify push succeeded
• Return push status

4. VALIDATE RESPONSE:

• Check handler returned success status
• Verify tag operation completed
• Capture tag details (name, sha, signed status)
• Confirm expected state changes

5. OUTPUT COMPLETION MESSAGE:

For Create:

✅ COMPLETED: Tag Manager - Create
Tag Created: {tag_name}
Commit: {commit_sha}
Signed: {signed}
Message: {message}
───────────────────────────────────────
Next: Push tag with push-tag operation or create release

For Push:

✅ COMPLETED: Tag Manager - Push
Tag Pushed: {tag_name} → {remote}
Remote URL: {remote_url}
───────────────────────────────────────
Next: Create GitHub release or trigger CI/CD pipeline