Progressive-depth codebase analysis and reverse engineering plugin for Claude Code
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when tracing turn loops, tool continuations, state transitions, or understanding how an AI agent or complex system actually processes requests through its execution cycle.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when understanding how source transforms to runtime, what gets filtered/compiled/generated, or tracing build-time shaping that affects what code actually runs.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when separating prompt-driven behavior from code-driven behavior, understanding what system prompts actually control vs what's hardcoded, or testing how behavior changes under different prompt configurations.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when evaluating code health, finding bug hotspots, identifying anti-patterns, preparing a quality improvement plan, or assessing technical debt.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when starting any codebase analysis to determine target type, feasibility, and which skills apply before investing tokens.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when distinguishing core modules from support/generated/test/infrastructure code, separating signal from noise, or understanding which parts of a repo actually matter for analysis.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when investigating implicit assumptions in code — ordering dependencies, unvalidated environment variables, assumed object shapes, or temporal state requirements that aren't enforced by types or tests.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when reducing codebase size, cleaning up before refactoring, investigating slow builds, or auditing for unused code and orphaned files.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when you have a written implementation plan to execute in a separate session with review checkpoints.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when investigating conditional tool availability, finding tools that exist but are hidden behind gates, or mapping the full capability surface of a system.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when onboarding to a new project, evaluating migration feasibility, auditing dependency health, or needing to know what technologies power a codebase.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when documenting public interfaces, planning API changes, evaluating backward compatibility, or understanding what a module exposes to consumers.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when you need to understand why capabilities differ across configurations, user types, or deployment environments, or when investigating feature flags and capability gates.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when needing component relationships, layer boundaries, module structure, or understanding how parts of a codebase fit together before modification or refactoring.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when you need to understand what a system was truly designed to become, where its real moat lies, or to produce a comprehensive analysis report combining all prior findings.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when predicting how a system behaves under different conditions, testing "what if" scenarios for gate combinations, or comparing behavioral fingerprints across configurations.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.