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

fix(cli): kilo local-path install leaves plugin rules inert

オープン
#1,081 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

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

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
72/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript
領域
cli

調査の方向性

Start in cli/src/contexts/tools/domain/profiles/kilo/profile.ts at the RulesCapability configuration, then compare it with the flat build strategy from #868 and the marketplace install behavior. Check how local-path installation and plugin remove handle rule paths; done means all-files Rules are installed at the top level, path-scoped Rules are skipped with a warning, and removal deletes exactly the installed files.

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

説明

Description

aidd plugin install <local plugin path> --tool kilo copies every plugin Rule verbatim into .kilo/rules/<plugin>/<name>.md, including path-scoped Rules with their paths frontmatter, and adds no instructions entry. Kilo never loads Rules placed there, so every Rule installed this way is inert. If anyone lists them, the path-scoped ones apply to every file, because Kilo ignores paths.

The marketplace install (aidd plugin install <name>, aidd setup) and the flat archive (aidd translate --to kilo --as flat) already handle this, through the flat build strategy delivered with #868 (PR #1069):

  • all-files Rules land at top-level .kilo/rules/<plugin>-<group>-<name>.md;
  • path-scoped Rules are skipped with a warning naming the Rule and its paths (install), or fail the build (translate).

The local-path install goes through the Kilo profile's RulesCapability instead, which predates that work.

Affected file(s)

cli/src/contexts/tools/domain/profiles/kilo/profile.ts (rules: new RulesCapability(...))

Expected behaviour

A local-path install for Kilo matches the marketplace install:

  • each all-files Rule is written to top-level .kilo/rules/<plugin>-<group>-<name>.md, so Kilo loads it;
  • each path-scoped Rule is skipped with the same warning;
  • plugin remove deletes exactly what the install wrote.
Observed behaviour

With a plugin holding 1 all-files Rule and 7 path-scoped Rules (aidd-craft), the install exits 0 and prints no warning:

  • all 8 Rules are copied to .kilo/rules/aidd-craft/, with their paths frontmatter;
  • .kilo/kilo.jsonc has no instructions key;
  • none of the 8 Rules reaches the model.

Measured on Kilo 7.7.5, real runtime, with a fake OpenAI-compatible server capturing the prompt:

  • a top-level .kilo/rules/*.md reaches the model without an instructions entry;
  • a file in .kilo/rules/<subdir>/ reaches it only when listed in instructions;
  • a Rule with paths: ["**/*.ts"] reaches a session that touches no .ts file, so paths is ignored.

Repro, from a CLI build of next, with an isolated HOME:

  1. Stage a marketplace (.claude-plugin/marketplace.json plus plugins/<plugin>/) whose plugin has one all-files Rule and one paths Rule.
  2. In a scratch git project, run aidd setup --ai kilo --plugins none --no-default-marketplace --yes.
  3. Run aidd plugin install <path-to-plugin> --tool kilo --yes.
  4. Run find .kilo/rules and grep instructions .kilo/kilo.jsonc.
AI tool

Kilo Code

aidd-cli version

5.5.0 (next, plus PR #1069)

OS

macOS 26.6.2

Additional context
主要言語
TypeScript
スター
481
フォーク
45
平均マージ
1日 2時間
マージ済み PR(30日)
77

環境構築

はじめの一歩

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

ai-driven-dev/framework のほかの issue

ai-driven-dev/framework の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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