Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[W9.5] Align the MCP tool, resource, and prompt catalogs with the current CLI

クローズ
#171 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
ruby
領域
cli, devtools, testing

調査の方向性

Start by comparing the exposed MCP tools and argument schemas with the current CLI, then trace schema-driven execution and the existing MCP discovery and behavior tests. Map supported tools, arguments, defaults, and CLI equivalents; identify unsupported commands and options. Done means supported workflows, prompts, and resources are aligned, pinning and offline behavior are verified, and each change has passing tests in its own PR.

索引モデルが issue の本文から書いたものです。

説明

area: cli enhancement

Context

The MCP catalog exposes a subset of OPSd commands and options. The current CLI also supports explicit module synchronization, platform rendering, and offline platform validation, so supported MCP workflows must be selected and described deliberately.

Scope

  • Compare all exposed tools and argument schemas with current CLI behavior.

  • Implement support for explicit modules sync, platform rendering, and offline validation where needed for the supported setup-to-render workflow.

  • Record intentionally unsupported CLI commands and options instead of implying full parity.

  • Update schemas, descriptions, reusable prompts, and resource pointers together.

  • Keep module synchronization explicit; render must not silently update dependency pins.

  • Extend schema and SDK-driven behavior tests in the same PR as each catalog/argument change. Verify discovery schemas and that exposed options reach actual execution, including module pin preservation and the documented offline behavior. Run these tests in the existing MCP CI suite.

Acceptance criteria

  • A documented mapping lists supported MCP tools, arguments, types, defaults, and relevant CLI equivalents.

  • The supported infrastructure and platform workflows have all prerequisites available through MCP or explicit documented setup steps.

  • Exposed options reach the execution layer and are covered by meaningful behavior tests.

  • Prompts and resources refer to existing commands, paths, and supported capabilities.

  • Offline behavior and module synchronization preserve the CLI pinning contract.

  • Each catalog/workflow change is delivered with passing discovery/schema and execution tests in its own PR; supported behavior is not left untested until W9.6.

Related

Parent: #166. Coordinate with #168 and #170.

主要言語
Ruby
スター
0
フォーク
0
平均マージ
11時間 37分
マージ済み PR(30日)
35

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

opsd-io/opsd-cli のほかの issue

opsd-io/opsd-cli の issue をすべて見る

似ている issue

Ruby の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。