Git Autopilot

Git Autopilot monitors your repository activity and automatically suggests or starts workflows based on git events.

Overview#

When you create a feature branch, commit with a specific prefix, or tag a release, Bootspring can automatically:

Suggest the appropriate workflow
Start the workflow (if auto-start is enabled)
Track the connection between git activity and workflows

How It Works#

Git Event          Pattern Match          Workflow Suggestion
─────────────────────────────────────────────────────────────
branch: feature/*  ───▶  feature/*   ───▶  Feature Development
commit: feat:      ───▶  feat:       ───▶  Feature Development
commit: security:  ───▶  security:   ───▶  Security Audit
files: prisma/*    ───▶  prisma/     ───▶  Database Migration
tag: v1.0.0        ───▶  v*          ───▶  Launch Preparation

Default Event Mappings#

Branch Patterns#

Pattern	Workflow
`feature/*`	feature-development
`fix/*`	feature-development
`hotfix/*`	security-audit
`release/*`	launch-preparation
`perf/*`	performance-optimization

Commit Message Patterns#

Prefix	Workflow
`feat:`	feature-development
`fix:`	feature-development
`security:`	security-audit
`perf:`	performance-optimization
`refactor:`	performance-optimization

File Change Patterns#

Files	Workflow
`prisma/*`	database-migration
`schema.prisma`	database-migration
`src/api/*`	api-development
`app/api/*`	api-development

Tag Patterns#

Pattern	Workflow
`v*`	launch-preparation
`release-*`	launch-preparation

Configuration#

Enable Autopilot#

# Enable with defaults
bootspring autopilot enable

# Enable with auto-start (no confirmation needed)
bootspring autopilot enable --auto-start

# Check status
bootspring autopilot status

Configuration Options#

// In bootspring.config.js
module.exports = {
  autopilot: {
    enabled: true,
    autoStart: false,           // Require confirmation before starting
    requireConfirmation: true,  // Show suggestions before acting
    ignoreBranches: ['main', 'master', 'develop'],
    eventMapping: {
      // Custom mappings
      'branch:docs/*': 'documentation-workflow',
      'commit:docs:': 'documentation-workflow',
    }
  }
};

Using Git Autopilot#

Viewing Suggestions#

When git events trigger suggestions:

# Check for suggestions
bootspring autopilot suggestions

# Output:
# Git Autopilot Suggestions:
#
# 1. feature-development (confidence: 0.8)
#    Trigger: branch 'feature/user-auth' matches 'feature/*'
#
# 2. database-migration (confidence: 0.6)
#    Trigger: file 'prisma/schema.prisma' modified
#
# Accept: bootspring autopilot accept feature-development
# Dismiss: bootspring autopilot dismiss feature-development

Accepting Suggestions#

# Accept and start a suggested workflow
bootspring autopilot accept feature-development

# Output:
# Started workflow: Feature Development
# Current Phase: Design
# Agents: ui-ux-expert, frontend-expert, api-expert

Dismissing Suggestions#

# Dismiss a suggestion
bootspring autopilot dismiss feature-development

Custom Event Mappings#

Adding Mappings#

# Add a custom mapping
bootspring autopilot map "branch:docs/*" "documentation-workflow"

# Add commit prefix mapping
bootspring autopilot map "commit:test:" "testing-workflow"

Removing Mappings#

# Remove a mapping
bootspring autopilot unmap "branch:docs/*"

API Usage#

const autopilot = require('bootspring/hooks/git-autopilot');

// Enable autopilot
autopilot.enable({ autoStart: false });

// Analyze current git state
const analysis = autopilot.analyzeGitState();
// {
//   enabled: true,
//   branch: 'feature/new-feature',
//   suggestions: [
//     { trigger: 'branch', workflow: 'feature-development', confidence: 0.8 }
//   ]
// }

// Accept a suggestion
autopilot.acceptSuggestion('feature-development');

// Add custom mapping
autopilot.addEventMapping('branch:custom/*', 'custom-workflow');

// Get status
autopilot.getStatus();

Best Practices#

Start with suggestions - Use requireConfirmation: true until you trust the mappings
Ignore protected branches - Keep main/master/develop in ignoreBranches
Use conventional commits - Autopilot works best with consistent commit prefixes
Review mappings regularly - Adjust as your workflow evolves