code-analysis

Analyze multi-language codebases for quality, complexity, and security risks.

Updated Aug 27, 2026

Search Tags:#security #codebase #dependencies #migration #complexity #static-analysis #analyze

Ready to run

npx skills add https://github.com/liushuang393/serverlessAIAgents --skill code-analysis-liushuang393

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-analysis
Source: https://github.com/liushuang393/serverlessAIAgents/tree/main/agentflow/skills/builtin/code_analysis
Command: npx skills add https://github.com/liushuang393/serverlessAIAgents --skill code-analysis-liushuang393

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates code analysis, complexity scoring, dependency mapping, security scanning, and migration planning to streamline refactoring and modernization projects.

Core Features & Use Cases

Static code analysis and quality assessment across languages.
Complexity scoring with hotspots, follow-up refactoring guidance.
Dependency mapping to reveal external/internal dependencies and risks.
Security scanning for SAST and dependency vulnerabilities.
Migration planning to generate phased upgrade strategies and actionable plans.

Quick Start

Run the code-analysis skill on a repository to obtain a structured report and a migration path.

Frequently Asked Questions about code-analysis

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

FAQPage Schema

How do I analyze a multi-language codebase for complexity hotspots and security risks?▼

To analyze a multi-language codebase for complexity hotspots and security risks, you can run static analysis and dependency mapping workflows. This surfaces quality scores, vulnerability scans, and structural hotspots, providing a cohesive report for targeted refactoring.

What is the best way to plan a safe migration and modernization path for a repository?▼

The best way to plan a safe migration is to generate a phased upgrade strategy based on static analysis and dependency graphs. This approach identifies structural risks and dependencies upfront, producing an actionable migration plan for modernization.

Can I map both internal and external dependencies to reveal vulnerability risks?▼

Yes, you can map both internal and external dependencies to reveal vulnerability risks. Dependency mapping scans the codebase to graph external libraries and internal modules, highlighting areas with SAST vulnerabilities and upgrade risks.

Does static code analysis provide refactoring guidance for high complexity areas?▼

Static code analysis does provide refactoring guidance for high complexity areas. By applying complexity scoring across the repository, it identifies specific hotspots and generates follow-up refactoring guidance to streamline code quality improvements.

When do I need to run a full codebase scan for SAST and dependency vulnerabilities?▼

You need to run a full codebase scan for SAST and dependency vulnerabilities before major refactoring or modernization projects. This security scanning identifies hidden risks in external dependencies and internal code, ensuring a safe migration path.