aurora-origin-merge

Name: aurora-origin-merge
Availability: InStock
Author: Avvale

Merge Aurora .origin.ts files into Angular code using YAML schema deltas.

1|Updated Jun 20, 2022

Search Tags:#frontend #angular #merge #origin.ts #yaml-delta #aurora-cli #code-customization

Ready to run

npx skills add https://github.com/avvale/aurora-front --skill aurora-origin-merge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aurora-origin-merge
Source: https://github.com/avvale/aurora-front/tree/main/.claude/skills/aurora-origin-merge
Command: npx skills add https://github.com/avvale/aurora-front --skill aurora-origin-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handles .origin.ts file merges after Aurora CLI regeneration in front-end projects. Provides step-by-step workflow to surgically merge new schema code into Angular files with custom modifications, preserving all business logic. Trigger: After aurora load front module creates .origin files, or when merging regenerated code with custom modifications.

Core Features & Use Cases

Provides a deterministic, step-by-step workflow to merge new schema-generated code into Angular files without overwriting manual changes.
Mirrors Aurora's origin-based implementation as the integration guide, ensuring business logic is preserved during regeneration.
Supports a YAML-delta-driven approach to distinguish newly introduced fields vs. intentionally removed ones and to preserve custom code.
Recommended tooling includes aurora-cli, aurora-development, and prettier.

Quick Start

Regenerate front-end code to produce .origin.ts files using the Aurora CLI.
Run the origin-merge workflow to integrate new schema into Angular files while preserving custom logic.
Review and test the merged code to ensure business logic remains intact.

Frequently Asked Questions about aurora-origin-merge

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

FAQPage Schema

How do I merge regenerated Angular code without losing custom modifications?▼

A deterministic merge workflow uses YAML schema deltas to distinguish newly introduced fields from intentionally removed ones, ensuring your custom Angular code and business logic remain intact during integration.

What is the best way to integrate .origin.ts files after Aurora CLI regeneration?▼

Integrating .origin.ts files after Aurora CLI regeneration involves mirroring Aurora's origin-based implementation as an integration guide, applying a defined merge order to surgically insert new schema code into existing Angular front-end files.

Can I preserve business logic when merging new schema-generated code into Angular?▼

Yes, you can preserve business logic by using a YAML-delta-driven approach to identify schema changes, which protects your manual modifications while safely merging the newly generated code into the Angular front-end project.

When do I need to use a YAML schema delta for merging front-end code?▼

You need to use a YAML schema delta for merging front-end code during post-regeneration workflows when Aurora CLI generates new .origin.ts files that must be integrated with existing custom modifications across multiple Angular files.

Does the origin merge workflow work with existing Angular customizations?▼

The origin merge workflow works directly with existing Angular customizations by enforcing a step-by-step process that targets post-regeneration workflows, safely integrating new schema code while preserving all your manual changes.

What tools are needed to safely merge .origin.ts files in a front-end project?▼

To safely merge .origin.ts files in a front-end project, the recommended tooling includes the Aurora CLI for generating origin files, the aurora-development environment, and Prettier for formatting the merged code output.