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

chore(dometrain): delete the dometrain-mcp plugin; the dotfiles own the Dometrain server

オープン
  • 何か問題がありますか？
#6,460 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

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

評価

難易度
3/5
見積もり時間
半日
初心者へのやさしさ
68/100
issue の種類
リファクタリング
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
json, markdown, shell
領域
developer-experience, documentation, tooling

調査の方向性

Delete plugins/dometrain-mcp/ and its marketplace.json entry. Then update every listed reference: .claude/settings.json (enabledPlugins), docs/catalog.md, docs/cloud-sessions.md, docs/migration-playbook.md, plugins/harness-ops/skills/machine-profile/scripts/profile.test.sh, and the plugins/dometrain/ README, plugin.json, setup/grounding/sync skill files. Bump the dometrain plugin version and add a CHANGELOG entry without rewriting old lines. Done when the plugin tree is gone, remaining docs point at claude mcp add-json or the official Dometrain plugin, and tests/docs no longer mention dometrain-mcp.

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

説明

Why

dometrain-mcp only wraps a 6-line remote server definition. The one thing it adds is entering the API key through a masked userConfig prompt.

  • No consumer: the owner's dotfiles register the same server (same name and URL) at user scope for every client, with the key from the vault. No other consumer is known.
  • Alternatives exist for anyone else: claude mcp add-json dometrain ... (already in the dometrain README), or Dometrain's official plugin (github.com/Dometrain/mcp).
  • It causes harm: two desktop setups had both the plugin server and the user-scope server, which registers the same server twice.

The adopt-and-adapt reason that justifies the dometrain skills plugin (keeping upstream skills in line with Anthropic's skill guidance) doesn't apply here, because there's no skill to adapt.

Policy for the owner's own plugins: no alias, no tombstone, no compat metadata. Delete it outright.

Scope (from the marketplace clone, 60 references across 16 files)

Delete:

  • plugins/dometrain-mcp/
  • its marketplace.json entry

Update references in:

  • .claude/settings.json (enabledPlugins)
  • docs/catalog.md, docs/cloud-sessions.md, docs/migration-playbook.md
  • plugins/harness-ops/skills/machine-profile/scripts/profile.test.sh
  • plugins/dometrain/:
    • README.md: the server section points at the one-line claude mcp add-json and at the official plugin
    • plugin.json description
    • skills/setup/SKILL.md and its evals
    • skills/grounding/SKILL.md:19-22
    • skills/sync/context/update.md

Bump dometrain's version and add a CHANGELOG entry. Don't rewrite its old CHANGELOG lines.

Coordination with the dotfiles

The dotfiles change lands in the same window, from the fleet plugin-unification PR:

  • uninstall dometrain-mcp@melodic-software on every machine
  • turn dometrain@melodic-software on
  • drop replacesPlugin from the dometrain row in .chezmoidata/mcp.yaml; it would point at nothing

Either order works. A machine still holding the plugin after this lands gets it removed at its next apply.

🤖 Generated with Claude Code

主要言語
Shell
スター
22
フォーク
2
平均マージ
5時間 11分
マージ済み PR（30日）
838

環境構築

はじめの一歩

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

melodic-software/claude-code-plugins のほかの issue

melodic-software/claude-code-plugins の issue をすべて見る

似ている issue

Shell/Bash の issue をもっと見る

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

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