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

design: plugin profiles (registry plus toggles, user, project and workload scopes)

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

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
18/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
shell
領域
developer-experience, tooling

調査の方向性

This is a design issue for plugin profiles (registry, user/project/workload scopes, named on/off maps) with open questions on dependency closure, CI --setting-sources, mid-session changes, and --settings vs claude-code-action merge. Start from native enabledPlugins and extraKnownMarketplaces in .claude/settings.json and --settings <file>. Related issues #6458, #6459, #6461 and anthropics/claude-code #90818/#91770. Done means a decided design, not a one-file patch.

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

説明

needs-triage

Goal

Switch which plugins load per task without installing or uninstalling anything.

  • Registry: the known marketplaces plus the installed plugins. Most plugins stay off.
  • Profile: a named on/off map applied to one session.

Requirements (owner, 2026-10-05)

  • User scope: an always-on core, the owner's own plugins.
  • Project scope: stack-specific marketplaces and plugins in the repo's .claude/settings.json, e.g. .NET plugins only in the .NET repo. Native today: enabledPlugins plus extraKnownMarketplaces.
  • Named profiles:
    • Session profiles: vanilla (all off), design, and others.
    • Workload profiles inside a project: GitHub Actions work in a .NET repo shouldn't load .NET plugins.
  • Native first, low coupling:
    • Apply with --settings <file>, which ranks above project and user settings and writes nothing to disk.
    • No separate config root, because that conflicts with account rotation.
    • Adopt any native profile feature when it ships. anthropics/claude-code #90818 and #91770 were open as of 2026-10-05.
  • Profile files: store them on disk with a skill that applies and manages them.

Measured evidence (2026-10-05, Claude Code 2.1.289, Haiku 4.5)

  • An installed plugin that no settings file enables does not load.
    • With every plugin off, the listing held 32 skills: built-in, user, and claude.ai-synced.
    • With the full config, it held 329.
  • The skill listing overflowed in every run: 317 of 329 descriptions were dropped. Fewer active plugins means better routing.
  • The real token costs are agent listings, SessionStart hook text (about 1.3k–1.4k tokens per plugin for some third-party ones) and MCP tool names. All melodic plugins together add about 4.6k tokens.

Open questions

  1. Dependency closure: 409 cross-plugin references, and only playgrounds declares dependencies. A profile must pull in every plugin its plugins call.
  2. Does a repo's enabledPlugins reach its CI review lanes when they don't pass --setting-sources?
  3. Can a profile change mid-session, or only at restart?
  4. How should --settings profiles interact with claude-code-action, which shallow-merges its settings input (an enabledPlugins key there replaces the whole map)?

Supersedes the closed #2034 (starter bundles).

Related:

  • #6458 (listing budget and descriptions)
  • #6459 (stock baseline)
  • #6461 (landscape audit)

🤖 Generated with Claude Code

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

環境構築

はじめの一歩

  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 を短くまとめたダイジェスト。