1. OUTPUT START MESSAGE:

🎯 STARTING: Cleanup Manager
Operation: {operation}
Filters: {filters}
───────────────────────────────────────

2. LOAD CONFIGURATION:

Load repo configuration to determine:

• Active handler platform (github|gitlab|bitbucket)
• Protected branches list
• Default inactivity threshold
• Cleanup policies

Use repo-common skill to load configuration.

3A. LIST STALE BRANCHES WORKFLOW:

Validate Inputs:

• Check inactive_days is positive number
• Validate location is valid (local|remote|both)
• Verify at least one filter enabled (merged or inactive)

Fetch Branch Information:

Invoke the active source control handler skill.

IMPORTANT: You MUST use the Skill tool to invoke the handler. The handler skill name is constructed as follows:

1. Read the platform from config: config.handlers.source_control.active (e.g., "github")
2. Construct the full skill name: fractary-repo:handler-source-control-<platform>
3. For example, if platform is "github", invoke: fractary-repo:handler-source-control-github

DO NOT use any other handler name pattern. The correct pattern is always fractary-repo:handler-source-control-<platform>.

Use the Skill tool with:

• command: fractary-repo:handler-source-control-<platform> (where is from config)
• Pass parameters: {merged, inactive_days, location}

The handler will return:

• Branch names
• Last commit date
• Last commit author
• Merge status (merged to default branch)
• Days since last activity

Filter Results:

If exclude_protected=true:

PROTECTED_BRANCHES = config.defaults.protected_branches
stale_branches = [b for b in branches if b.name not in PROTECTED_BRANCHES]

Apply Filters:

• Merged filter: Include only fully merged branches
• Inactive filter: Include branches with last commit > N days ago
• Combine filters (AND or OR based on configuration)

Sort Results:

• Sort by days inactive (oldest first)
• Group by merge status
• Separate local and remote branches

Generate Report:

## Stale Branches Report

### Fully Merged Branches ({count})
- feat/123-old-feature (merged 45 days ago, last commit: 2024-09-15)
- fix/456-auth-bug (merged 60 days ago, last commit: 2024-08-31)

### Inactive Branches ({count})
- chore/789-update-deps (90 days inactive, last commit: 2024-08-01)

### Total: {total_count} stale branches

**Safe to Delete**: {merged_count} merged branches
**Review Required**: {inactive_count} inactive but unmerged branches

3B. DELETE BRANCH WORKFLOW:

Validate Branch Name:

• Check branch_name is non-empty
• Verify branch exists in specified location
• Validate location is valid

CRITICAL: Check Protected Branches:

PROTECTED_BRANCHES = config.defaults.protected_branches
if branch_name in PROTECTED_BRANCHES:
    ERROR: "CRITICAL: Cannot delete protected branch: {branch_name}"
    EXIT CODE 10

Check Merge Status:

If force=false:

• Verify branch is fully merged to default branch
• Check for unmerged commits
• Warn if branch has unique commits

if not fully_merged and not force:
    ERROR: "Branch has unmerged commits: {branch_name}. Use force=true to delete anyway."
    EXIT CODE 13

Dry Run Mode:

If dry_run=true:

• Show what would be deleted
• Display branch details
• Return without making changes

DRY RUN: Would delete branch {branch_name} from {location}
- Last commit: {last_commit_date}
- Merge status: {merged_status}
- Location: {location}

Confirmation:

If not dry_run:

• Show branch details
• Require explicit confirmation (unless autonomous mode)
• Provide option to cancel

Invoke Handler:

IMPORTANT: You MUST use the Skill tool to invoke the handler. The handler skill name is constructed as follows:

1. Read the platform from config: config.handlers.source_control.active (e.g., "github")
2. Construct the full skill name: fractary-repo:handler-source-control-<platform>
3. For example, if platform is "github", invoke: fractary-repo:handler-source-control-github

DO NOT use any other handler name pattern. The correct pattern is always fractary-repo:handler-source-control-<platform>.

Use the Skill tool with:

• command: fractary-repo:handler-source-control-<platform> (where is from config)
• Pass parameters: {branch_name, location, force}

The handler will:

• Delete branch from local repository (if location includes local)
• Delete branch from remote repository (if location includes remote)
• Return deletion status

Verify Deletion:

• Confirm branch no longer exists in target locations
• Check for any errors or warnings
• Capture deletion details

4. VALIDATE RESPONSE:

• Check handler returned success status
• Verify operation completed as expected
• Capture affected branches
• Confirm expected state changes

5. OUTPUT COMPLETION MESSAGE:

For List:

✅ COMPLETED: Cleanup Manager - List
Stale Branches Found: {count}
- Merged: {merged_count}
- Inactive: {inactive_count}
───────────────────────────────────────
Review the list above and use delete-branch to clean up

For Delete:

✅ COMPLETED: Cleanup Manager - Delete
Branch Deleted: {branch_name}
Location: {location}
Status: {fully_merged ? "Merged" : "Forced"}
───────────────────────────────────────
Branch cleanup completed successfully