What problem does it solve?
Adding a new compile-time suggestion or diagnostic to the Reactor DSL requires coordinating a Roslyn analyzer, a CLI mirror rule, release tracking rows, parity tests, and generated docs — a process where false positives and analyzer/CLI drift are easy to introduce. This Skill orchestrates that entire workflow so contributors ship correct REACTOR_* diagnostics without breaking the build.
Core Features & Use Cases
- Analyzer authoring: Implements new
REACTOR_* Roslyn diagnostics in src/Reactor.Analyzers/ under netstandard2.0 constraints, gated by semantic-model symbol matching rather than raw syntax text.
- CLI parity: Mirrors each rule in
src/Reactor.Cli/Check/ with reflection-discovered registration and parity tests so analyzer and mur check behavior cannot drift.
- False-positive spiking: Validates candidate matches against realistic negative code before implementation, since a did-you-mean that fires on valid code is worse than no rule.
- Use Case: A contributor asks to add a did-you-mean suggestion when a developer mistypes a Reactor factory name; the Skill spikes the fuzzy match, implements the analyzer plus CLI rule, adds the
AnalyzerReleases.Unshipped.md row, runs the analyzer and check test suites, and syncs the generated docs template.
Quick Start
Ask the assistant to add a REACTOR_ diagnostic that suggests the correct factory when a developer mistypes a Reactor DSL method name.
