static-analysis

Name: static-analysis
Availability: InStock
Author: vivekmano27

Run tool-based static analysis to report duplication, complexity, dead code, and code smells.

Updated Mar 14, 2026

Search Tags:#complexity #code-quality #duplication #static-analysis #semgrep #dead-code #jscpd

Ready to run

npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill static-analysis-vivekmano27

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: static-analysis
Source: https://github.com/Vivekmano27/agent-orchestrator/tree/main/plugins/project-orchestrator/skills/static-analysis
Command: npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill static-analysis-vivekmano27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automates the detection of code quality issues across projects by orchestrating established static analysis tools for duplication, complexity, dead code, and code smells. It helps maintain code health in polyglot codebases without manual, repeated runs.

Core Features & Use Cases

Tool orchestration: Runs duplication, complexity, dead code, and smells checks using language-appropriate tools (jscpd, semgrep, eslint, ruff, detekt, knip, vulture, deadcode) based on project configuration.
Project-aware scope: Applies only to the project's tech stack as defined in project-config.md, avoiding irrelevant analyses.
Output & reporting: Produces structured findings (JSON/Markdown) suitable for review and integration into CI dashboards.

Quick Start

Run a full static analysis against the current project to surface code smells and quality hotspots.

Frequently Asked Questions about static-analysis

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

FAQPage Schema

How do I run static code analysis across a polyglot codebase?▼

To run static code analysis across a polyglot codebase, configure project-config.md to define your tech stack, and the tool orchestrates language-appropriate analyzers to detect duplication, complexity, dead code, and smells automatically.

What is the best way to detect duplicate code and dead code simultaneously?▼

Detecting duplicate code and dead code simultaneously requires orchestrating tools like jscpd and vulture. This static analysis approach validates required analyzers and outputs structured findings for both issues in a consistent review format.

Does this static analysis tool work with multiple languages like Python and JavaScript?▼

Yes, static analysis works with multiple languages like Python and JavaScript by applying project-aware scope. It runs language-appropriate tools such as ruff for Python and eslint for JavaScript based on your project configuration.

Can I use semgrep for code smell detection in my project?▼

You can use semgrep for code smell detection within this static analysis workflow. The tool orchestrates semgrep alongside other analyzers to identify quality issues and outputs structured findings in JSON or Markdown formats.

How do I format static analysis findings for CI dashboard integration?▼

Formatting static analysis findings for CI dashboard integration involves running the orchestrated analysis to produce structured outputs. The tool generates consistent JSON and Markdown reports suitable for direct review and dashboard integration.

Why does static analysis only run specific tools for my tech stack?▼

Static analysis runs specific tools for your tech stack to apply a project-aware scope, avoiding irrelevant analyses. It reads your project-config.md to validate required analyzers and ensure only language-appropriate tools execute.