analyzer-agent

Perform read-only static analysis and security scanning of codebases.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Unicorn/Radium --skill analyzer-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzer-agent
Source: https://github.com/Unicorn/Radium/tree/main/skills/specialized/analyzer-agent
Command: npx skills add https://github.com/Unicorn/Radium --skill analyzer-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides systematic, read-only static analysis and security scanning to uncover bugs, vulnerabilities, and maintainability issues across a codebase, reducing manual review effort and missed risks.

Core Features & Use Cases

  • Static Analysis: Inspect code structure, patterns, and potential defects without modifying files.
  • Security Scanning: Identify common vulnerability patterns, unsafe usages, and risky dependencies.
  • Code Metrics & Quality: Calculate complexity, test coverage indicators, and adherence to best practices.
  • Use Case: Run during CI, pre-merge reviews, or periodic audits to produce prioritized, evidence-backed findings for engineering teams.

Quick Start

Ask the analyzer-agent to perform a read-only static analysis of the repository and summarize critical security and maintainability issues with file-level evidence.

Frequently Asked Questions about analyzer-agent

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

FAQPage Schema
How do I perform static analysis and security scanning on a codebase?

Static analysis and security scanning can be performed by applying read-only inspection tools to your software repository to identify bugs, vulnerabilities, and maintainability issues without modifying files. This process evaluates code quality and detects anti-patterns using lint and search tools.

Can I automate code review and linting in my CI pipeline?

Yes, you can automate code review and linting by running static analysis during CI pipelines or pre-merge pull request reviews. This systematically evaluates code metrics, detects risky dependencies, and produces prioritized, evidence-backed findings to reduce manual review effort.

What is static analysis for secure and maintainable code?

Static analysis for secure and maintainable code is a read-only inspection process that uncovers bugs, vulnerabilities, and maintainability issues across a codebase. It calculates code metrics, identifies common vulnerability patterns, and checks adherence to best practices to reduce missed risks.

Does static analysis modify files when detecting anti-patterns?

No, static analysis restricts operations to read-only analysis and lint/search tools to detect anti-patterns. It inspects code structure, identifies potential defects, and provides file-level findings with evidence-linked recommendations without modifying your actual software repository files.

What's the best way to prioritize bug fixes during a code audit?

The best way to prioritize bug fixes during a code audit is to run systematic static analysis and security scanning to generate evidence-linked recommendations. This approach evaluates code quality and highlights critical security vulnerabilities and maintainability issues with file-level findings.