What happens if a conflict occurs in the model manager?

The skill establishes a 'Keep Azure Features' priority, ensuring that methods like with_azure_endpoint() and is_azure() are preserved even if upstream changes model handling.

How do I verify the merge was successful?

The skill provides a post-merge checklist including compilation checks, full test suites, and specific UI feature verification for themes and syntax highlighting.

Does it support selective cherry-picking?

Yes, it includes a 4-step process to identify 'safe' commits that do not touch Azure-modified files, allowing for conflict-free synchronization.

Why use this skill instead of a standard git merge?

Standard merges often overwrite specialized Azure configurations and Claude/Anthropic support; this skill provides specific guidance and scripts to prioritize preserving those critical features.

Azure Codex Merge Upstream

Name: Azure Codex Merge Upstream
Author: Arthur742Ramos

byArthur742Ramos

0•

Developer Tools

Synchronizes Azure Codex forks with upstream OpenAI Codex repositories while protecting specialized Azure features and UI enhancements.

This skill provides a specialized framework for developers maintaining the Azure Codex fork to pull in the latest updates from the upstream OpenAI Codex repository. It automates and guides the complex process of merging or cherry-picking upstream commits while ensuring that critical Azure-specific components—such as Entra ID authentication, Anthropic model support, and custom TUI themes—remain intact and functional. It includes pre-merge checklists, selective cherry-picking scripts, and post-merge testing protocols to maintain stability.

Key Features

010 GitHub stars

02Preservation of Claude/Anthropic endpoint handling and SSE parsing

03Automated conflict resolution prioritization for Azure-specific components

04Protection for Azure Entra ID, Managed Identity, and Service Principal auth

05Post-merge validation suite for UI themes and syntax highlighting

06Selective cherry-picking logic to identify 'safe' upstream commits

Use Cases

01Performing safe upstream updates when the fork and main repo have diverged significantly

02Resolving complex merge conflicts in model management and configuration files

03Syncing a fork with new OpenAI Codex features without breaking Azure Auth

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add arthur742ramos/azure-codex merge-upstream

For use in Claude.ai and ChatGPT

Key Features

010 GitHub stars

02Preservation of Claude/Anthropic endpoint handling and SSE parsing

03Automated conflict resolution prioritization for Azure-specific components

04Protection for Azure Entra ID, Managed Identity, and Service Principal auth

05Post-merge validation suite for UI themes and syntax highlighting

06Selective cherry-picking logic to identify 'safe' upstream commits

Use Cases

01Performing safe upstream updates when the fork and main repo have diverged significantly

02Resolving complex merge conflicts in model management and configuration files

03Syncing a fork with new OpenAI Codex features without breaking Azure Auth

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add arthur742ramos/azure-codex merge-upstream

For use in Claude.ai and ChatGPT