add-feature
01Skill Claude CodeCodex
Guide for adding a new feature to OhMyCode. Use when user wants to add functionality that goes beyond existing extension points (tools/providers). Always start by reading docs/DEVELOPMENTGUIDE.md.
Skill Claude CodeCodex
Guide for adding a new feature to OhMyCode. Use when user wants to add functionality that goes beyond existing extension points (tools/providers). Always start by reading docs/DEVELOPMENTGUIDE.md.
Skill Claude CodeCodex
Guide for adding a new LLM provider to OhMyCode. Use when user wants to connect a new AI model backend.
Skill Claude CodeCodex
Guide for adding a new tool to OhMyCode. Use when user wants to create a custom tool.
Skill Claude CodeCodex
OhMyCode commit message conventions. MUST load on every git commit — provides Conventional Commits format with scope inference from file paths.
Skill Claude CodeCodex
Guide for customizing OhMyCode's terminal output style and rendering. Use when user wants to change colors, formatting, or how responses look in the terminal.
Skill Claude CodeCodex
Guide for customizing OhMyCode's AI personality and behavior via system prompt. Use when user wants to change how the AI behaves, its tone, or its instructions.
Skill Claude CodeCodex
Guide for debugging OhMyCode issues. Use when user reports errors, unexpected behavior, or connection problems.
Skill Claude CodeCodex
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Skill Claude CodeCodex
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Skill Claude CodeCodex
Use when you have a written implementation plan to execute in a separate session with review checkpoints.
Skill Claude CodeCodex
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session.
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
Skill Claude CodeCodex
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification.
Skill Claude CodeCodex
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions.
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code.
Skill Claude CodeCodex
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
Skill Claude CodeCodex
Run OhMyCode benchmarks — score any provider/model with token tracking. Use when user wants to benchmark, evaluate, test performance, or compare models.
Skill Claude CodeCodex
Generate high-quality tests for OhMyCode modules. Use when user wants to create, add, or generate tests for a module or file.
Skill Claude CodeCodex
Run tests and analyze results for OhMyCode. Use when user wants to run, check, or verify tests — or after any code change.