omx-setup

Install and configure oh-my-codex for user or project directories.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/RJJJJ/project2 --skill omx-setup-rjjjj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omx-setup
Source: https://github.com/RJJJJ/project2/tree/main/.codex/skills/omx-setup
Command: npx skills add https://github.com/RJJJJ/project2 --skill omx-setup-rjjjj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to install or refresh oh-my-codex for the current project and user-level OMX directories, streamlining environment setup and consistency across environments.

Core Features & Use Cases

  • Resolve setup scope for user or project, persist scope state, and adapt installation mode (legacy vs plugin) based on the environment.
  • Create and configure local project directories, merge or generate configuration, and provide safe defaults for CI/local development.
  • Support interactive prompts or non-interactive defaults, while handling migrations and safety checks to avoid overwrites.

Quick Start

Run omx setup to install or refresh oh-my-codex for the current project and user directories.

Frequently Asked Questions about omx-setup

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

FAQPage Schema
How do I set up oh-my-codex for a new local development project?

oh-my-codex setup scope is resolved for either the user directory or the current project root, persisting scope state and adapting the installation mode between legacy and plugin configurations.

Can I configure oh-my-codex non-interactively for CI pipelines?

Yes, you can configure oh-my-codex non-interactively by using default settings during setup, which applies safe defaults for CI and local development without requiring interactive prompts.

Does the omx setup process migrate existing configurations safely?

Yes, the setup process handles migrations and performs safety checks to prevent accidental overwrites, ensuring your existing configuration files are safely merged or updated.

What is the difference between project and user scope when installing oh-my-codex?

Installing oh-my-codex at the project scope writes configuration to the local project root, while user scope configures the user-level OMX directories to streamline environment consistency.

Why does my oh-my-codex setup switch between legacy and plugin mode?

The setup adapts the installation mode between legacy and plugin based on the detected environment, enforcing current CLI behavior and updating configuration to match.