The /merge command performs an intelligent merge between workflows you’ve customized for your project and the latest updates from the Governed Catalog. It aims to preserve your unique logic (like custom deployment steps) while integrating system-wide improvements.
Command Syntax
/merge [workflow-name]Detailed Execution Flow
1. Semantic Analysis
The Agent reads both files (Local and Catalog) to identify:
- Customizations: Changes you’ve made (e.g., added notification triggers, specific Slack channels).
- Updates: New catalog features (e.g., optimized prompts, new CLI command integration).
2. Merge Strategy
The system applies three core rules:
- Preserve: KEEPS all project-specific steps and custom logic.
- Inject: ADDS new sections or improvements from the catalog that don’t conflict with local code.
- Update: Automatically upgrades deprecated syntax (legacy paths or legacy flags).
3. Verification & Application
A backup file (.bak) is created before overwriting. Post-merge, the Agent displays a summary of what was PRESERVED, INJECTED, or UPGRADED for your final approval.
Relationships
/install— Often initiates this flow when conflicts arise./para-workflow— View available versions in the global catalog.