// Quality gates checklist for completing code work before finishing implementation cycles
| name | code-completion |
| description | Quality gates checklist for completing code work before finishing implementation cycles |
Run before finishing any implementation cycle.
Before running quality gates:
Console.WriteLine, breakpoints).bak, .new, .debug.*)dotnet format --severity info --no-restore
npx markdownlint-cli2 --fix
Zero errors and zero warnings required. Individual checks:
dotnet tool run roslynator fix --properties TargetFramework=net10.0 --severity-level hidden --verbosity normal
dotnet format --severity info --no-restore
npx markdownlint-cli2 --fix
VS Code task: Lint: All (fix)
dotnet build "Stock.Indicators.sln" -v minimal --nologo
VS Code task: Build: .NET Solution (incremental)
dotnet test "Stock.Indicators.sln" --no-restore --nologo
VS Code task: Test: Unit tests
When changing indicators or public APIs:
docs/indicators/{IndicatorName}.mddocs/migration.md for notable and breaking changes from v2src/Obsolete.V3.*.cs for deprecated APIsdotnet format --verify-no-changes --severity info --no-restore
dotnet build "Stock.Indicators.sln" -v minimal --nologo
dotnet test "Stock.Indicators.sln" --no-build --nologo
npx markdownlint-cli2
Do not ignore, defer, or suppress warnings.
New or updated indicators require:
*.StaticSeries.cs*.Catalog.cs + registration*.Tests.cs with full coveragedocs/indicators/{Name}.mdWhen changing public APIs:
[Obsolete] with migration messagedocs/migration.mdsrc/Obsolete.V3.Indicators.cs and src/Obsolete.V3.Other.csSee references/quality-gates.md for the quick reference table of all commands and configuration file locations.
Implement StreamHub real-time indicators with O(1) performance. Use for ChainHub or QuoteProvider implementations. Covers provider selection, RollbackState patterns, performance anti-patterns, and comprehensive testing with StreamHubTestBase.
Format and validate Markdown files following GitHub Flavored Markdown standards with automated linting and manual semantic review
Create and register indicator catalog entries for automation. Use for Catalog.cs files, CatalogListingBuilder patterns, parameter/result definitions, and PopulateCatalog registration.
Implement Series-style batch indicators with mathematical precision. Use for new StaticSeries implementations or optimization. Series results are the canonical reference—all other styles must match exactly. Focus on cross-cutting requirements and performance optimization decisions.
Write and update the VitePress documentation website for stock indicators. Use when adding a new indicator page, updating an existing indicator page, or making structural changes to the docs site.
Implement BufferList incremental indicators with efficient state management. Use for IIncrementFromChain or IIncrementFromQuote implementations. Covers interface selection, constructor patterns, and BufferListTestBase testing requirements.