fix(plh): downgrade cross-plugin command-name overlap to low ambiguity
Commands are namespaced (/name:command), so a command name shared by two differently-named plugins keeps both reachable — it is ambiguity, not a hard conflict. The check now mirrors COL's plugin-vs-plugin skill finding: severity LOW (was HIGH), category plugin-hygiene, COL-shaped details.namespaces, and a group-first shape (one finding per command name listing every namespace, not pairwise). It keys on the declared namespace (was folder basename) and fires only across 2+ distinct namespaces — when plugins share a declared name, the namespace-collision finding (medium) is the right signal, so this stays silent. Removes the inaccurate "only one wins" humanizer entry. Adds fixtures (duplicate-command-name; a shared command in duplicate-plugin-name's colliding namespace) and 4 tests. Suite 932->936. self-audit A 97 / A 100, scanners 13.
This commit is contained in:
parent
c6c5f17752
commit
0874188fe4
13 changed files with 160 additions and 27 deletions
|
|
@ -12,7 +12,7 @@
|
|||

|
||||

|
||||

|
||||

|
||||

|
||||

|
||||
|
||||
A Claude Code plugin that checks configuration health, suggests context-aware improvements, and auto-fixes issues — `CLAUDE.md`, `settings.json`, hooks, rules, MCP servers, `@imports`, and plugins. 13 deterministic scanners across 10 quality areas, context-aware feature recommendations, auto-fix with backup/rollback, a prompt-cache-aware Token Hotspots scanner with optional API-calibrated `--accurate-tokens` mode, plus cache-prefix stability, dead-tool, and cross-plugin collision detection. Zero external dependencies.
|
||||
|
|
@ -350,8 +350,11 @@ By default, `/config-audit` auto-detects scope from your git context. Override w
|
|||
> one plugin's commands, skills, and agents are silently shadowed and become unreachable.
|
||||
> The standalone plugin-health scanner (PLH) flags this at **medium** severity, keying on the
|
||||
> declared `name` field rather than the folder name (the folder name is irrelevant to the
|
||||
> namespace). Skill-name overlaps across *different* namespaces are a separate, lower-severity
|
||||
> concern owned by the COL scanner.
|
||||
> namespace). A *command* name shared by two **differently-named** plugins is a milder case —
|
||||
> namespacing keeps both reachable as `/a:cmd` and `/b:cmd`, so it is only ambiguity in error
|
||||
> messages, search results, and the command listing. PLH reports that at **low** severity
|
||||
> (group-first, one finding per command name), mirroring the COL scanner, which owns the
|
||||
> analogous skill-name overlaps across *different* namespaces.
|
||||
|
||||
### CLI Tools
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue