run-inspection

Name: run-inspection
Availability: InStock
Author: orekyuu

Execute static code analysis and plan fixes for code quality issues.

Updated Feb 28, 2026

Search Tags:#code quality #static analysis #debugging #refactoring #maintenance #code inspection

Ready to run

npx skills add https://github.com/orekyuu/orekyuu-claude-plugins --skill run-inspection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: run-inspection
Source: https://github.com/orekyuu/orekyuu-claude-plugins/tree/main/plugins/mcp-ide-gateway/skills/run-inspection
Command: npx skills add https://github.com/orekyuu/orekyuu-claude-plugins --skill run-inspection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of identifying code quality issues through static analysis and helps in planning the necessary fixes, improving overall code health and maintainability.

Core Features & Use Cases

Static Analysis: Detects errors, warnings, and style issues in your codebase.
Scope Definition: Allows analysis of specific files, classes, or the entire project.
Fix Planning: Generates actionable plans to address identified code quality problems.
Use Case: When you need to ensure your code adheres to quality standards before a release, use this skill to perform a thorough inspection and get a clear roadmap for improvements.

Quick Start

Run an inspection on the current project to find and plan fixes for all warnings and errors.

Frequently Asked Questions about run-inspection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run static code analysis to identify quality issues before a release?▼

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.

Can I analyze only the recently modified files instead of the entire project?▼

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.

What is the best way to plan fixes for code quality problems detected during an inspection?▼

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.

Does static code inspection support filtering by severity level?▼

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.

How do I define the scope for a codebase inspection?▼

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.

When should I use automated code inspection over manual code review?▼

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.