refactor: レビューと PR コメント対応の Skill を統合 (0-2)

.serena/project.yml

@@ -1,39 +1,4 @@
 
-# list of languages for which language servers are started (LSP backend only); choose from:
-# ada al angular ansible bash
-# bsl clojure cpp cpp_ccls crystal
-# csharp csharp_omnisharp cue dart elixir
-# elm erlang fortran fsharp gdscript
-# go groovy haskell haxe hlsl
-# html java json julia kotlin
-# latex lean4 lua luau markdown
-# matlab msl nix ocaml pascal
-# perl php php_phpactor php_phpantom powershell
-# python python_jedi python_pyrefly python_ty r
-# rego ruby ruby_solargraph rust scala
-# scss solidity svelte swift systemverilog
-# terraform toml typescript typescript_vts vue
-# yaml zig
-# (This list may be outdated; generated with scripts/print_language_list.py;
-# For the current list, see values of Language enum here:
-# https://github.com/oraios/serena/blob/main/src/solidlsp/ls_config.py)
-# For some languages, there are alternative language servers, e.g. csharp_omnisharp, ruby_solargraph.)
-# Note:
-# - For C, use cpp
-# - For JavaScript, use typescript
-# - For Angular projects, use angular (subsumes typescript+html; requires `npm install` in the project root)
-# - For Svelte projects, use svelte (subsumes typescript/javascript for .svelte projects; requires npm)
-# - For SCSS / Sass / plain CSS, use scss (some-sass-language-server handles all three)
-# - For Free Pascal/Lazarus, use pascal
-# Special requirements:
-# Some languages require additional setup/installations.
-# See here for details: https://oraios.github.io/serena/01-about/020_programming-languages.html#language-servers
-# When using multiple languages, the first language server that supports a given file will be used for that file.
-# The first language is the default language and the respective language server will be used as a fallback.
-# Note that when using the JetBrains backend, language servers are not used and this list is correspondingly ignored.
-languages:
-- bash
-
 # the encoding used by text files in the project
 # For a list of possible encodings, see https://docs.python.org/3.11/library/codecs.html#standard-encodings
 encoding: "utf-8"
@@ -43,6 +8,13 @@ ignore_all_files_in_gitignore: true
 
 # list of additional paths to ignore in this project.
 # Same syntax as gitignore, so you can use * and **.
+# Important: quote patterns that start with `*`, otherwise YAML treats them as aliases.
+# Example:
+# ignored_paths:
+# - "examples/**"
+# - ".worktrees/**"
+# - "**/bin/**"
+# - "**/obj/**"
 # Note: global ignored_paths from serena_config.yml are also applied additively.
 ignored_paths: []
 
@@ -166,3 +138,38 @@ activation_command:
 # maximum time in seconds to wait for activation_command to complete before killing it (default 180s).
 # must be a positive number.
 activation_command_timeout: 180.0
+
+# list of language servers to start when using the LSP backend; choose from:
+# ada al angular ansible bash
+# bsl clojure cpp cpp_ccls crystal
+# csharp csharp_omnisharp cue dart elixir
+# elm erlang fortran fsharp gdscript
+# go groovy haskell haxe hlsl
+# html java json julia kotlin
+# latex lean4 lua luau markdown
+# matlab msl nix ocaml pascal
+# perl php php_phpactor php_phpantom powershell
+# python python_basedpyright python_jedi python_pyrefly python_ty
+# qml r rego ruby ruby_solargraph
+# rust scala scss solidity svelte
+# swift systemverilog terraform toml typescript
+# typescript_vts vue yaml zig
+# (This list may be outdated; generated with scripts/print_language_list.py;
+# For the current list, see values of the LanguageServerId enum here:
+# https://github.com/oraios/serena/blob/main/src/solidlsp/ls_config.py)
+# For some languages, there are several alternative language servers, e.g. csharp_omnisharp, ruby_solargraph.)
+# Note:
+# - For C, use cpp
+# - For JavaScript, use typescript
+# - For Angular projects, use angular (subsumes typescript+html; requires `npm install` in the project root)
+# - For Svelte projects, use svelte (subsumes typescript/javascript for .svelte projects; requires npm)
+# - For SCSS / Sass / plain CSS, use scss (some-sass-language-server handles all three)
+# - For Free Pascal/Lazarus, use pascal
+# Special requirements:
+# Some language servers require additional setup/installations.
+# See here for details: https://oraios.github.io/serena/01-about/020_programming-languages.html#language-servers
+# When using multiple language servers, the first language server that supports a given file will be used for that file.
+# The first language server is the default language and the respective language server will be used as a fallback.
+# Note that when using the JetBrains backend, language servers are not used and this list is correspondingly ignored.
+language_servers:
+- bash

.serena/serena_config.yml

@@ -103,6 +103,7 @@ projects:
 # list of paths to ignore across all projects.
 # Same syntax as gitignore, so you can use * and **.
 # These patterns are merged additively with each project's own ignored_paths.
+# Quote patterns that start with `*`, e.g. `"**/bin/**"`.
 ignored_paths: []
 
 # time budget (seconds) per tool call for the retrieval of additional symbol information
@@ -191,7 +192,22 @@ jetbrains_launch_command:
 # - /home/user/projects/**
 # - C:\Users\Anna\Dev\work\**
 # The pattern "**" matches any project path, so it can be used to trust all projects.
-# NOTE: リポジトリにコミットする設定では信頼対象を空にしておく。
-# 任意の project.yml の trusted 限定設定（activation_command / ls_specific_settings 等）を
-# 無条件に受け入れないようにするため。信頼が必要な場合は各自のローカル設定で指定する。
 trusted_project_path_patterns: []
+
+# mapping from language server keys to integer priority values (higher = more preferred), which determine
+# language server selection during automatic project creation and are used to break ties when multiple
+# language servers match an equal number of source files.
+# The priority values override Serena's default priorities:
+# * 0 = experimental or secondary language servers, which are never auto-detected
+# (e.g. `python_*` and `php_*` are "secondary"; also applies to non-programming languages like `json`)
+# * 1 = supersets of other languages, which shall be preferred only if they match more files
+# (e.g. `vue` and `svelte`, which are supersets of `typescript`)
+# * 2 = default priority
+# Example:
+# ls_priorities:
+# python: 0
+# python_basedpyright: 3
+# This example would achieve that `python_basedpyright` becomes the preferred language server for Python,
+# giving it a high priority of 3, while the default Python language server is fully excluded from
+# auto-detection with priority 0.
+ls_priorities:

README.md

@@ -8,9 +8,9 @@ Claude Code / Codex / Kiro CLI向けのスキル・MCP設定を共有するた
 
 **NDFプラグイン v4.20.1** は、同じ `ndf@ai-plugins` という名前で Claude Code / Codex / Kiro CLI へ配布されるランタイム別プラグインです。共通ソースは `plugins/ndf-shared/` に集約し、利用者が install する配布物は `plugins/ndf-claude/` / `plugins/ndf-codex/` / `plugins/ndf-kiro/` に分かれています。
 
-- **公開Skills**: Claude Code向け core 27個、Kiro向け core 26個、Codex向け core 27個に分離。
-- **元Skills（36個）**:
- - PR/レビューワークフロー (12): pr, pr-tests, fix, review, review-branch, review-pr-comments, resolve-pr-comments, cherry-pick-pr, deploy, sync-main, merged, clean
+- **公開Skills**: Claude Code向け core 24個、Kiro向け core 23個、Codex向け core 24個に分離。
+- **元Skills（33個）**:
+ - PR/レビューワークフロー (9): pr, pr-tests, fix, review, cherry-pick-pr, deploy, sync-main, merged, clean
  - 原則・ガイドライン (10): ndf-policies, branch-fix-strategy, implementation-plan, plan-to-spec, investigation-rules, problem-solving, logging-guidelines, markdown-writing, issue-plan-strategy, ml-model-structure
  - データ分析・品質・環境 (5): qa-security-scan, docker-container-access, google-auth, codex, official-skills-autoloader
  - E2Eテスト/Playwright (4): playwright-planning, playwright-authoring, playwright-evidence, playwright-kit-ops
@@ -100,7 +100,7 @@ kiro-cli chat
 
 | プラグイン名 | バージョン | 説明 | 詳細 |
 |------------|----------|------|------|
-| **ndf** | 4.20.1 | Claude Code / Codex / Kiro CLI 向けに runtime 別配布物を提供する NDF プラグイン。8個の専門エージェント（Claude版）、公開Skills（Claude Code向け core 29個、Kiro向け core 28個、Codex向け core 30個）、Claude SessionStart/Stopフック、Codex/Kiro向け通知・実行補助を提供。v4.0.0 で Codex MCP サーバを廃止し、`/ndf:codex` skill + `corder` エージェント経由の CLI 直接実行に一本化。 | [Claude](./plugins/ndf-claude/README.md) / [Codex](./plugins/ndf-codex/README.md) / [Kiro](./plugins/ndf-kiro/README.md) |
+| **ndf** | 4.20.1 | Claude Code / Codex / Kiro CLI 向けに runtime 別配布物を提供する NDF プラグイン。8個の専門エージェント（Claude版）、公開Skills（Claude Code向け core 26個、Kiro向け core 25個、Codex向け core 27個）、Claude SessionStart/Stopフック、Codex/Kiro向け通知・実行補助を提供。v4.0.0 で Codex MCP サーバを廃止し、`/ndf:codex` skill + `corder` エージェント経由の CLI 直接実行に一本化。 | [Claude](./plugins/ndf-claude/README.md) / [Codex](./plugins/ndf-codex/README.md) / [Kiro](./plugins/ndf-kiro/README.md) |
 
 ### NDF v4.20.1 の主な変更
 

docs/ndf-plugin-reference.md

@@ -64,7 +64,7 @@ NDF の Skill 実装は `plugins/ndf-shared/skills/` が編集元です。公開
 
 主な Skill 領域:
 
-- PR / review workflow: `pr`, `pr-tests`, `fix`, `review`, `cross-review`, `resolve-pr-comments`
+- PR / review workflow: `pr`, `pr-tests`, `fix`, `review`, `cross-review`
 - branch / release workflow: `deploy`, `cherry-pick-pr`, `sync-main`, `merged`, `clean`
 - planning / documentation: `implementation-plan`, `issue-plan-strategy`, `plan-to-spec`, `markdown-writing`
 - quality / execution: `playwright-*`, `docker-container-access`

plugins/ndf-claude/.claude-plugin/plugin.json

@@ -46,9 +46,6 @@
  "./skills/sync-main",
  "./skills/cherry-pick-pr",
  "./skills/deploy",
- "./skills/review-branch",
- "./skills/review-pr-comments",
- "./skills/resolve-pr-comments",
  "./skills/playwright-authoring",
  "./skills/codex",
  "./skills/gemini",

plugins/ndf-claude/skills/cross-review/SKILL.md

@@ -468,10 +468,9 @@ pint / larastan / test / build などは **中断** を原則とする。
 ## 関連
 
 - `/ndf:review` — 単発レビュー（AI 直接投稿対応）
-- `/ndf:fix` — 修正対応（サブエージェント起動対応）
+- `/ndf:fix` — 指摘の分類・修正・返信・Resolve（サブエージェント起動対応）
 - `/ndf:codex` — codex CLI 呼び出し手順
 - `/ndf:gemini` — gemini CLI 呼び出し手順
-- `/ndf:resolve-pr-comments` — Resolve Conversation の詳細
 - `/ndf:issue-plan-strategy` — multi-PR ワークフローでは **個別 PR ごとに本 cross-review が原則必須**。
  `/ndf:review` 単発や Claude Code の `code-reviewer` は代替にせず、release ブランチへ merge する前に
  codex + gemini の APPROVE 収束を確認する (Step 6)