code-analyze

Static analysis on .NET solutions uses Roslyn analyzers and StyleCop to automatically detect code quality violations. This Skill runs these tools across your project, applies security and dependency checks, and generates a report without modifying source code, suitable for pre-commit checks and CI pipelines.

Yes. This Skill automates secret detection, vulnerability scanning, and NuGet dependency checks on .NET solutions. It identifies exposed secrets, vulnerable packages, and outdated dependencies, producing an analysis report with metrics and exit codes for integration into automated workflows.

Roslyn analyzers are compiler-based tools that catch errors and code issues at compile time; StyleCop enforces style and consistency rules. This Skill runs both together to surface code quality issues comprehensively—Roslyn catches functional problems, StyleCop enforces standards.

This Skill performs non-intrusive analysis: it restores, builds, and scans your .NET solution with analyzers, security tools, and dependency checks, then generates a report and exit code. No source changes occur, making it ideal for automated code review gates in CI systems.

No. Dependency checks automatically scan NuGet packages for known vulnerabilities and outdated versions, surfacing risks in your project's dependency graph. This Skill integrates those checks into your analysis workflow to ensure dependency hygiene without manual effort.

Analysis produces an analysis_report document, exit codes for CI integration, and metrics summarizing code quality, security findings, and vulnerable dependencies. This structured output enables downstream tooling, notifications, and dashboards to act on discovered issues.