template-update

Template-update applies changes to marketplace templates as the authoritative source, then identifies consumer repositories that need re-auditing. It validates syntax, preserves structure and comments, and returns the updated template path, content, and affected repositories for downstream remediation.

Yes. Template-update tracks which consumer repositories depend on each template and flags them for re-audit after changes. This ensures downstream systems pick up the updated configuration without manual intervention.

Template-update includes built-in validation that checks syntax and integrity before templates propagate. Invalid updates are rejected, so consumers only receive verified, working templates.

When an audit detects template drift, template-update pushes corrected templates to the marketplace first, then remediates affected consumer repositories. This audit-triggered workflow keeps templates and configs synchronized.

Yes. Template-update applies to config skills and domain skills that use templates. It locates template directories, validates updates, and handles remediation across all consumer repositories that reference them.

Template-update returns the updated template path, the new template content with preserved structure, and a list of affected repositories. Use this list to track which consumers need re-auditing or downstream actions.