code-analyzer

Purpose

Give the user a clear, prioritized picture of the health of their project: what's broken, what's risky, what's messy, what's missing, and what could be added. The output is a structured report — not a pile of speculation. Every finding points at a real file, names the concern in plain terms, and proposes a direction.

This is a diagnostic skill, not a refactor skill. Do not edit code, run formatters, or commit anything as part of the audit. Only after the user reads the report and explicitly picks something to fix do you change code.

When to use

• User asks for a project review, audit, code quality check, or general "what's wrong with this codebase"
• User asks about security issues, vulnerabilities, or hardening across the project
• User asks "what could be improved" or "what should I work on next"
• User asks for new feature ideas grounded in the existing project
• Hungarian equivalents: "nézd át", "auditáld", "találj hibákat", "javasolj fejlesztéseket"

If the user has a specific bug or feature in mind ("fix this crash", "add this endpoint"), that is not this skill — handle it directly.

Prerequisites