run-inspection

Static code analysis identifies errors, warnings, and style issues by scanning your codebase. This skill automates the inspection process and generates actionable fix plans to ensure your code adheres to quality standards before release.

Yes, you can analyze recently modified files. When scope is not explicitly defined, the skill dynamically resolves the scope using Git-modified files to focus the static analysis on your recent changes.

The best way to plan fixes for code quality problems is to use an automated inspection planner. This skill integrates a planner subagent that generates a clear roadmap of actionable steps to address detected issues.

Static code inspection supports severity level filtering. This allows you to narrow the analysis scope to specific thresholds of errors and warnings, ensuring you focus on the most critical code quality issues first.

You can define the inspection scope by specifying target files, classes, or the entire project. A scope resolver subagent ensures the static analysis accurately targets your defined boundaries.

Automated code inspection should be used when you need to quickly detect style issues and errors across large scopes. It provides a structured fix plan that improves maintainability before a release, complementing manual review efforts.