Code Completion
Testing & Qualitycode-completionCode Completion is an Agent Skill for testing & quality published in the facioquo/stock-indicators-dotnet repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Quality gates checklist for completing code work before finishing implementation cycles
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/facioquo/stock-indicators-dotnet/blob/HEAD/.agents/skills/code-completion/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/code-completion, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Code completion checklist
Run before finishing any implementation cycle.
Workflow
Step 0: Remove dead code
Before running quality gates:
- Delete obsolete or commented-out code
- Remove unused imports, variables, helper methods
- Strip debugging aids (
Console.WriteLine, breakpoints) - Remove scratch files (
.bak,.new,.debug.*)
Step 1: Run linters
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)
Step 2: Build
dotnet build "Stock.Indicators.sln" -v minimal --nologo
VS Code task: Build: .NET Solution (incremental)
Step 3: Test
dotnet test "Stock.Indicators.sln" --no-restore --nologo
VS Code task: Test: Unit tests
Step 4: Update documentation
When changing indicators or public APIs:
- Update XML documentation for changed public APIs
- Update
docs/indicators/{IndicatorName}.md - Update
docs/migration/v3.mdfor notable and breaking changes from v2 - Update
src/Obsolete.V3.*.csfor deprecated APIs
Step 5: Verify
dotnet 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
Quality standards
- Zero linting errors and zero warnings
- Zero build warnings and errors
- All tests pass (coverage ≥ 98% validated in CI/CD)
- Documentation updated for public API changes
- Migration bridges updated for breaking changes
Do not ignore, defer, or suppress warnings.
Indicator components
New or updated indicators require:
- Series:
{Indicator}.Series.cspartial class file - Catalog:
*.Catalog.cs+ registration - Tests:
*Tests.cswith full coverage - Docs:
docs/indicators/{Name}.md - Regression baseline (if algorithm changed)
- Performance benchmark (complex indicators)
Migration bridge
When changing public APIs:
- Add
[Obsolete]with migration message - Update
docs/migration/v3.md - Update
src/Obsolete.V3.Indicators.csandsrc/Obsolete.V3.Other.cs
See references/quality-gates.md for the quick reference table of all commands and configuration file locations.