Meridian.Analyzer 0.2.3

Meridian.Analyzer

Meridian.Analyzer is a Roslyn analyzer package for backend readability, architecture, security, reliability, and performance rules.

Quick Start

Install the published analyzer package into a consumer project:

dotnet add package Meridian.Analyzer

Or add an explicit package reference:

<ItemGroup>
  <PackageReference Include="Meridian.Analyzer" Version="0.2.*" PrivateAssets="all" />
</ItemGroup>

Repository Layout

• src/Meridian.Analyzer/: analyzer project, rule implementations, helpers, and Roslyn release tracking files
• tests/Meridian.Analyzer.Tests/: analyzer behavior tests
• docs/: maintainer guidance, examples, and per-rule documentation
• LICENSE: MIT license for the repository and published package metadata

Documentation

• Usage examples: docs/usage-example.md
• Maintainer guide: docs/guide.md
• Rule docs: docs/rules/MER0001.md
• Rule docs: docs/rules/MER0002.md
• Rule docs: docs/rules/MER0003.md
• Rule docs: docs/rules/MER0004.md
• Rule docs: docs/rules/MER0005.md
• Rule docs: docs/rules/MER0006.md
• Rule docs: docs/rules/MER0007.md
• Rule docs: docs/rules/MER0008.md
• Rule docs: docs/rules/MER0009.md
• Rule docs: docs/rules/MER0010.md
• Rule docs: docs/rules/MER0011.md
• Rule docs: docs/rules/MER0012.md
• Rule docs: docs/rules/MER0013.md
• Rule docs: docs/rules/MER0014.md
• Rule docs: docs/rules/MER0015.md
• Rule docs: docs/rules/MER0016.md
• Rule docs: docs/rules/MER0017.md
• Rule docs: docs/rules/MER0018.md
• Rule docs: docs/rules/MER0019.md
• Rule docs: docs/rules/MER0020.md
• Rule docs: docs/rules/MER0021.md
• Rule docs: docs/rules/MER0022.md
• Rule docs: docs/rules/MER0023.md
• Rule docs: docs/rules/MER0024.md
• Rule docs: docs/rules/MER0025.md

Current Surface

• Analyzer project: src/Meridian.Analyzer/Meridian.Analyzer.csproj
• Test project: tests/Meridian.Analyzer.Tests/Meridian.Analyzer.Tests.csproj
• Diagnostic prefix: MER
• Category namespaces: Meridian.Readability, Meridian.Security, Meridian.Architecture, Meridian.Reliability, Meridian.Performance
• Packaging status: published on nuget.org

Validation Entry Points

• Local test run: dotnet test tests/Meridian.Analyzer.Tests/Meridian.Analyzer.Tests.csproj -c Release
• Local package smoke check: dotnet pack src/Meridian.Analyzer/Meridian.Analyzer.csproj -c Release -o artifacts

Use dotnet test and dotnet pack from this repo to validate the standalone package itself.

Consumer Configuration

Configure analyzer severities in your consuming project's .editorconfig:

[*.cs]
dotnet_diagnostic.MER0001.severity = warning
dotnet_diagnostic.MER0002.severity = warning

You can enable only the rules you want. Each rule document describes the contract it enforces and the preferred refactor shape.

Risks And Current Boundaries

• nuget.org is public. The current publish lane is fine for public distribution, but it is not a private feed.
• Release automation depends on the NUGET_KEY GitHub secret. If that key rotates or loses push scope, the release workflow will fail at publish time.
• Some rules encode opinionated architectural conventions. Review the rule docs before enabling large sets as build warnings in an existing codebase.

Current Rules

Rule-Addition Checklist

Before landing MER0002+ or any later rule, update these surfaces in the same change:

1. Analyzer implementation under src/Meridian.Analyzer/
2. Positive and negative tests under tests/Meridian.Analyzer.Tests/
3. Rule documentation under docs/rules/
4. The rule index in this README.md
5. docs/guide.md or docs/usage-example.md when the maintainer workflow changed