dev-verify

Automated code verification across .NET and Angular projects runs build, test, lint, and security analysis phases sequentially. This unified process detects quality issues in both stacks and provides an interactive interface to apply selective or global code fixes.

Post-change checks for .NET and Angular code quality are best handled by a unified verification loop that executes builds, tests, security scans, and formatting automatically. It eliminates manual overhead by presenting detected issues in an interactive menu for immediate remediation.

Yes, local CLI tools are required to run automated testing and linting for Angular and .NET. You must have dotnet, ng, and standard linting utilities installed and integrated locally to perform deterministic code fixes and execute the verification phases.

Yes, you can selectively apply fixes when linting or build errors are detected. The verification process presents a clear report of identified issues and allows you to selectively or globally apply fixes with a single command through an interactive menu.

Unified post-change verification handles security analysis by executing security scan phases automatically alongside builds, tests, and formatting for backend and frontend stacks. Detected security issues are then routed into the interactive fix menu for remediation.

Automated code quality checks should be run after refactoring shared services or before committing changes, replacing manual linting. This ensures deterministic execution of all backend and frontend tests, security scans, and formatting rules across the entire stack simultaneously.