sync-workflow

Incrementally merge artifacts, extract ASTs, and update graphs for AICA repositories.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/smitkhanparaZuru/AI-Coding-Automation --skill sync-workflow-smitkhanparazuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-workflow
Source: https://github.com/smitkhanparaZuru/AI-Coding-Automation/tree/main/.github/skills/sync-workflow
Command: npx skills add https://github.com/smitkhanparaZuru/AI-Coding-Automation --skill sync-workflow-smitkhanparazuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incremental Sync Workflow reduces waste by updating only the changed parts of a codebase during repository synchronization, avoiding full rebuilds whenever possible.

Core Features & Use Cases

  • Incremental merging of detector outputs to keep artifacts fresh
  • Incremental AST extraction for changed files and selective graph updates
  • Intelligent fallback to full rebuild when changes exceed a configurable threshold
  • Optional embedding updates and CI/CD integration for automated pipelines

Quick Start

Run aica sync-repo after code changes to trigger an incremental update of detectors, AST data, graph, and embeddings.

Frequently Asked Questions about sync-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid full repository rebuilds when syncing frequent code changes?

Incremental repository sync updates only the changed parts of a codebase, merging artifacts and re-extracting ASTs for changed files to avoid full rebuilds whenever possible.

How does incremental AST extraction work for large TypeScript projects?

Incremental AST extraction targets changed files and selectively updates the graph, ensuring that only modified TypeScript or TSX code is re-processed during the sync workflow.

Can I configure a fallback threshold for full rebuilds in CI/CD pipelines?

Yes, the sync workflow implements an intelligent fallback to a full rebuild when code changes exceed a configurable threshold, automating safe CI/CD pipeline updates.

How do I trigger an incremental update for ASTs, graphs, and embeddings after code changes?

Run the sync command after code changes to trigger an incremental update of detectors, AST data, graph structures, and optionally refresh embeddings.

When should I use incremental merging of detector outputs over a complete re-synchronization?

Use incremental merging of detector outputs for large codebases with frequent changes where full re-synchronization is too costly, keeping artifacts fresh without redundant processing.