Skip to content

/analyze

Comprehensive code analysis across quality, security, performance, and architecture domains

From plugin
claude-scholar
5.5k65 skills6 agents65 commands5 hooks
Install
> /plugin marketplace add Galaxy-Dawn/claude-scholar
> /plugin install claude-scholar@claude-scholar

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/analyze

Context preview

What this command does when you run it.

Comprehensive code analysis across quality, security, performance, and architecture domains

Command definition

analyze.md
name: analyze
description: "Comprehensive code analysis across quality, security, performance, and architecture domains"
category: utility
complexity: basic
mcp-servers: []
personas: []

/sc:analyze - Code Analysis and Quality Assessment

Triggers

  • Code quality assessment requests for projects or specific components
  • Security vulnerability scanning and compliance validation needs
  • Performance bottleneck identification and optimization planning
  • Architecture review and technical debt assessment requirements

Usage

/sc:analyze [target] [--focus quality|security|performance|architecture] [--depth quick|deep] [--format text|json|report]

Behavioral Flow

1. **Discover**: Categorize source files using language detection and project analysis 2. **Scan**: Apply domain-specific analysis techniques and pattern matching 3. **Evaluate**: Generate prioritized findings with severity ratings and impact assessment 4. **Recommend**: Create actionable recommendations with implementation guidance 5. **Report**: Present comprehensive analysis with metrics and improvement roadmap

Key behaviors:

  • Multi-domain analysis combining static analysis and heuristic evaluation
  • Intelligent file discovery and language-specific pattern recognition
  • Severity-based prioritization of findings and recommendations
  • Comprehensive reporting with metrics, trends, and actionable insights

Tool Coordination

  • **Glob**: File discovery and project structure analysis
  • **Grep**: Pattern analysis and code search operations
  • **Read**: Source code inspection and configuration analysis
  • **Bash**: External analysis tool execution and validation
  • **Write**: Report generation and metrics documentation

Key Patterns

  • **Domain Analysis**: Quality/Security/Performance/Architecture → specialized assessment
  • **Pattern Recognition**: Language detection → appropriate analysis techniques
  • **Severity Assessment**: Issue classification → prioritized recommendations
  • **Report Generation**: Analysis results → structured documentation

Examples

Comprehensive Project Analysis

/sc:analyze
# Multi-domain analysis of entire project
# Generates comprehensive report with key findings and roadmap

Focused Security Assessment

/sc:analyze src/auth --focus security --depth deep
# Deep security analysis of authentication components
# Vulnerability assessment with detailed remediation guidance

Performance Optimization Analysis

/sc:analyze --focus performance --format report
# Performance bottleneck identification
# Generates HTML report with optimization recommendations

Quick Quality Check

/sc:analyze src/components --focus quality --depth quick
# Rapid quality assessment of component directory
# Identifies code smells and maintainability issues

Boundaries

**Will:**

  • Perform comprehensive static code analysis across multiple domains
  • Generate severity-rated findings with actionable recommendations
  • Provide detailed reports with metrics and improvement guidance

**Will Not:**

  • Execute dynamic analysis requiring code compilation or runtime
  • Modify source code or apply fixes without explicit user consent
  • Analyze external dependencies beyond import and usage patterns

**Output**: Analysis report containing:

  • Severity-rated findings
  • Code quality metrics
  • Security vulnerabilities
  • Performance issues
  • Recommendations

**Next Step**: After review, use `/sc:improve` to apply recommended fixes or `/sc:cleanup` for dead code removal.

Read more
Ships withclaude-scholar

Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.

Get the whole plugin, auto-invoked

Other commands on claude-scholar.