analyze-code

Analyze code for bugs, architecture, performance, and security issues.

1|Updated Oct 26, 2025
One-click install
npx skills add https://github.com/yangsi7/fine-tuning-exercise-generation --skill analyze-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-code
Source: https://github.com/yangsi7/fine-tuning-exercise-generation/tree/main/.claude/skills/analyze-code
Command: npx skills add https://github.com/yangsi7/fine-tuning-exercise-generation --skill analyze-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill performs efficient, intelligence-first code analysis to diagnose bugs, understand architecture, identify performance bottlenecks, and assess security. By querying metadata before reading files, it drastically reduces token usage and speeds up investigation.

Core Features & Use Cases

  • Intelligence-First Approach: Utilizes project-intel.mjs to search for relevant files, analyze symbols, and trace dependencies, achieving 80-95% token savings compared to direct file reading.
  • Comprehensive Analysis Types: Supports bug diagnosis (e.g., infinite re-renders), architecture analysis (e.g., circular dependencies), and performance analysis (e.g., N+1 queries).
  • MCP Verification & CoD^Σ Trace: Verifies findings against authoritative sources (e.g., React docs) and generates a complete Chain-of-Thought (CoD^Σ) trace for transparent, evidence-backed conclusions.
  • Use Case: If a user reports "LoginForm re-renders infinitely," this Skill will efficiently pinpoint the root cause (e.g., an incomplete useEffect dependency array at src/components/LoginForm.tsx:47), provide evidence, and recommend a fix, all while minimizing token cost.

Quick Start

Use the analyze-code skill to investigate why 'src/components/UserList.tsx' is loading slowly.

Frequently Asked Questions about analyze-code

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

FAQPage Schema
How do I diagnose bugs in my code without reading every file?

Code analysis uses metadata queries to pinpoint bugs like infinite re-renders or logic errors by searching symbols and dependencies first, reducing token usage by 80-95% compared to direct file inspection.

Can I identify performance bottlenecks like N+1 queries in my project?

Performance analysis traces query patterns and dependency chains across your codebase to locate bottlenecks, then provides evidence-backed recommendations for optimization.

What's the best way to trace circular dependencies in a large codebase?

Dependency tracing queries project metadata to map symbol references and circular imports, generating a complete trace report with file locations and chain-of-thought evidence.

How do I verify security issues are real before fixing them?

Security analysis checks findings against authoritative sources and generates a CoD^Σ trace with supporting evidence, so you know exactly what to fix and why.

Does this work for understanding architecture issues like tight coupling?

Architecture analysis identifies structural problems like circular dependencies and tight coupling by analyzing symbols and dependencies, producing a detailed trace report with specific file locations.