メニュー
Guidelines for using the OpenSpec CLI tool in non-interactive environments. Use this skill when validating specifications or changes to ensure commands run successfully without user intervention.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Switch oh-my-opencode.json model configurations between different modes using YAML-based mapping definitions
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.
| name | openspec-cli |
| description | Guidelines for using the OpenSpec CLI tool in non-interactive environments. Use this skill when validating specifications or changes to ensure commands run successfully without user intervention. |
| metadata | {"short-description":"Run OpenSpec validation non-interactively"} |
This skill provides instructions for using the openspec command-line interface (CLI) effectively within the MCP environment, where interactive prompts are not supported.
The default openspec validate command triggers an interactive mode which will cause the agent to hang or fail. Use the following explicit commands instead:
To validate the entire project:
openspec validate --all
To validate only the currently changed files (useful for quick checks):
openspec validate --changes
To validate only the specification files:
openspec validate --specs
To validate a specific item by name:
openspec validate <item-name>