analyze
Systematic multi-step codebase analysis producing prioritized findings with file-line evidence. Covers architecture reviews, security assessments, and code quality evaluations through guided exploration, investigation planning, and synthesis. Use when you say "analyze this codebase", "run security assessment", "architecture review of this system", "find code smells", or "review code quality" across multiple files. Do NOT use for single-file maintainability scoring (use code-qualities-assessment) or CWE-78 injection pattern scanning (use security-scan).
- License
- MIT
Pinned to revision acff1d0a1f21, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/analyze/SKILL.md
- skills/analyze/references/DEVELOPMENT.md
- skills/analyze/references/agent-architecture-patterns.md
- skills/analyze/references/context-budget-management.md
- skills/analyze/references/design-legacy-code.md
- skills/analyze/references/design-tell-dont-ask.md
- skills/analyze/references/engineering-complexity-tiers.md
- skills/analyze/references/quality-boy-scout-rule.md
- skills/analyze/references/reliability-observability-pillars.md
- skills/analyze/references/strategy-ooda-loop.md
- skills/analyze/scripts/analyze.py
Every link opens the file at its source, pinned to the revision this page describes.