Back to Signal Feed
CodeTracked since May 19, 2026

dotnet-test merges smell-detection into test-anti-patterns to remove plugin activation conflict

Variant C of PR #672 removes `test-smell-detection` as a separate skill and makes `test-anti-patterns` the single smell-audit entry point, moving the smell catalog and four evaluation scenarios into that skill’s suite so plugin-mode activation is no longer split between competing siblings.

dotnet-testtest-anti-patternstest-smell-detectionplugin-mode activation

What Happened

  • Variant C of PR #672 removes `test-smell-detection` as a separate skill and makes `test-anti-patterns` the single smell-audit entry point, moving the smell catalog and four evaluation scenarios into that skill’s suite so plugin-mode activation is no longer split between competing siblings.
  • Variant C of PR #672 removes `test-smell-detection` as a separate skill and makes `test-anti-patterns` the single smell-audit entry point, moving the smell catalog and four evaluation scenarios into that skill’s suite so plugin-mode activation is no longer split between competing siblings.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

This change fixes plugin-mode activation correctness by consolidating overlapping smell-audit behavior into one public skill: `test-anti-patterns` now owns the smell-audit triggers, catalog, and eval coverage previously split with `test-smell-detection`, which had caused sibling competition during activation.

Why Track This

Why It Matters

Developers and operators running plugin-mode audits should see more reliable activation behavior in dotnet test smell checks, because one overlapping skill was removed and the remaining smell checks now route through a single entry point. Technically, `test-smell-detection` is deleted, its 19-smell catalog is moved under `test-anti-patterns/references`, and its four eval scenarios/fixtures are ported into the `test-anti-patterns` suite; README and `test-quality-auditor` references are also updated to reflect the new canonical skill. This is a breaking change for consumers that explicitly target `test-smell-detection`, so watch for downstream configs/scripts still calling it, and track plugin selection/validation results to confirm no regressions in smell coverage or invocation semantics.

Impact

Developers and operators running plugin-mode audits should see more reliable activation behavior in dotnet test smell checks, because one overlapping skill was removed and the remaining smell checks now route through a single entry point. Technically, `test-smell-detection` is deleted, its 19-smell catalog is moved under `test-anti-patterns/references`, and its four eval scenarios/fixtures are ported into the `test-anti-patterns` suite; README and `test-quality-auditor` references are also updated to reflect the new canonical skill. This is a breaking change for consumers that explicitly target `test-smell-detection`, so watch for downstream configs/scripts still calling it, and track plugin selection/validation results to confirm no regressions in smell coverage or invocation semantics.

What To Watch Next

  • Watch whether dotnet-test becomes a repeated pattern.
  • Track follow-up changes around Code Repository Intelligence.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: breaking_removal_of_public_skill, downstream_references_to_deleted_skill.
Open Topic TimelineOpen Technical EventOpen Original Sourcebreaking_removal_of_public_skill / downstream_references_to_deleted_skill / regression_in_plugin_activation_for_edge_requests / evaluation_coverage_drift

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

dotnet/skills PR #672: test-anti-patterns: merge test-smell-detection in (Variant C)

Validation shows plugin skill count drops from 22 to 21 after deleting `test-smell-detection`, moving its references/cases into `test-anti-patterns`, and updating `plugins/dotnet-test` docs/config references.