sync

SpecForge Sync Command

Synchronize your codebase after manual changes to OpenAPI spec or database schema. This command detects changes and regenerates code to keep everything in sync.

Overview

The sync command is useful when:

1. You've manually edited spec/openapi.yaml
2. You've added/modified database migrations
3. You've pulled changes from version control that include spec updates
4. You need to regenerate code after resolving merge conflicts

Sync orchestrates:

• Detecting spec changes since last sync
• Validating updated specifications
• Regenerating type-safe code from schemas
• Identifying affected handlers that need updates
• Running tests to verify everything still works

Sync Process

Step 1: Detect Changes

Identify what has changed since the last successful build:

# Check for OpenAPI spec changes
if [ -f spec/openapi.yaml ]; then
    echo "Checking OpenAPI spec for changes..."
    # Compare with last known state (stored in .specforge/last-sync.json)
fi

# Check for new database migrations
echo "Checking for new migrations..."
ls -t migrations/*.sql | head -5

# Check for schema changes in existing migrations
git diff HEAD~1 migrations/ 2>/dev/null || echo "Not a git repository or no previous commits"

Categorize changes:

• OpenAPI only: New/modified endpoints, schemas, examples
• Database only: New migrations, schema alterations
• Both: Coordinated changes to API and database

Step 2: Validate Updated Specifications

Validate OpenAPI Spec

Use the openapi-expert skill:

Invoke openapi-expert skill with:
- action: "validate-spec"
- spec_path: "spec/openapi.yaml"

Validation checks:

• Valid OpenAPI 3.x syntax
• All $ref references resolve
• Request/response schemas are valid
• Examples match schemas
• No duplicate operation IDs
• Descriptions include business logic details

Validate Database Schema

Read SpecForge configuration to identify database plugin:

grep "database:" CLAUDE.md | cut -d: -f2 | tr -d ' '