القائمة
Switch oh-my-opencode.json model configurations between different modes using YAML-based mapping definitions
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | oh-my-opencode-model-switcher |
| description | Switch oh-my-opencode.json model configurations between different modes using YAML-based mapping definitions |
| metadata | {"short-description":"Switch oh-my-opencode model configurations"} |
This skill enables switching model configurations in oh-my-opencode.json between different modes:
opencode/glm-4.7-freeAdditional modes can be easily added by editing the mapping configuration.
When the user requests to switch models or activate a specific mode, use this skill to update the configuration.
Execute the switch script with the desired mode:
python3 ~/.config/opencode/.claude/model-switcher/scripts/switch_models.py [mode_name]
Examples:
python3 ... switch_models.py economy - Switch to economy modepython3 ... switch_models.py default - Switch to default modepython3 ~/.config/opencode/.claude/model-switcher/scripts/switch_models.py --list
config/model-mappings.yml"*" to apply a model to all agents/categoriesvariant are kept unchangedEdit config/model-mappings.yml to:
Example mapping structure:
modes:
mode_name:
agents:
agent_name: model_name
# or use "*" for all agents
categories:
category_name: model_name
Create and maintain DBML files for systems that split data across a PrimaryDB and one or more ClientDB instances. Use when adding or updating DBML for multi-database schemas, tenant-specific client databases, cross-database analysis views, logical relationships based on business keys such as ProjectNo, or recommended dbml folder structures.
Cross-repository code review for multi-repo web applications. Use when reviewing changes across multiple repositories to detect inconsistencies in API contracts, type definitions, dependencies, or integration points that single-repo reviews might miss. Triggers on phrases like 'review across repositories', 'check multi-repo changes', 'cross-repo code review', or when working with VSCode workspaces containing multiple project folders.
Create a pull request from current development branch to origin/main (not upstream/main). Use when you need to merge a feature branch into the main branch of your fork and want to ensure the PR targets origin/main with English descriptions. Always confirms remote target with user before creation to prevent accidentally creating PRs to upstream repositories.
Create standardized business operation manuals, procedures, and documentation following corporate guidelines. Use this skill when the user needs to create or update business documents such as release procedures, work instructions, operation manuals, regulations, or standard operating procedures (SOPs). Triggers include requests like "業務マニュアル作成", "手順書を書いて", "operation manual", "create procedure document", or when standardized business documentation is needed.
Transform technical article drafts or source materials into human-like, high-quality Japanese technical articles. Use this skill when the user wants to generate, rewrite, or humanize technical articles (especially about TypeScript, JavaScript, React, or frontend topics) following specific human-writing patterns and style guidelines. Triggers include requests like "記事を人間風に", "tech article を生成", "humanize this article", or providing article source materials.
Generate clear, professional, and polished Japanese technical articles suitable for corporate blogs, official documentation, and technical publications. Use this skill when the user wants to create enterprise-level content with consistent polite tone (です/ます), logical structure, and authoritative voice. Triggers include requests like "polished article", "professional tone", "enterprise blog", "公式ドキュメント", "プロフェッショナルな記事", or when content needs formal technical writing.