aurora-origin-merge_skill

Overview

This skill handles .origin.ts file merges that appear after Aurora CLI regeneration in front-end Angular projects. It provides a step-by-step workflow to surgically merge regenerated schema code into existing files while preserving all custom business logic. Use it to ensure new schema fields are added, removed, or ignored correctly based on the YAML delta.

How this skill works

First detect the YAML schema delta via git to classify fields as NEW, MODIFIED, or DELETED. For each .origin.ts file, compare the generated .origin version with the existing custom file and apply changes guided by the YAML delta. The process uses the .origin file as an implementation guide, applying imports, injections, properties, form controls, template elements, GraphQL updates, and column entries in a controlled order while preserving custom code.

When to use it

• After running aurora load front module and finding .origin.ts files
• When Aurora CLI regenerated files but custom modifications exist
• When you need to safely merge new schema fields without losing business logic
• Before committing changes that include Aurora-generated diffs
• When a schema change might add or remove GraphQL or UI fields

Best practices

• Always run git diff on the module YAML first to produce NEW/MODIFIED/DELETED lists
• Compare each .origin with the existing file — never replace the custom file wholesale
• Apply changes in the prescribed order (imports, injections, properties, form controls, template, columns, GraphQL, resolver types)
• Preserve every line of custom code; only add or remove code justified by the YAML delta
• Delete .origin files after merging and run Prettier and TypeScript checks

Example use cases

• A backend change adds a new field in the module YAML and Aurora created .origin files—merge the new form control, template field, GraphQL field, and column entry.
• A field was intentionally removed from the schema earlier—verify YAML delta and do not re-add it from .origin.
• A developer added custom initialization logic in a component—preserve that logic while adding new observable properties from .origin.
• Multiple regenerated files reference a new relation—update resolver return types and relation queries first to avoid runtime errors.