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.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when you have a specific suspicion about a codebase and want targeted analysis to confirm or deny it with evidence, rather than exploratory analysis.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when repo origin is unclear, dealing with leaks/sourcemaps/decompiled code, or needing to distinguish source of truth from derived, generated, or reconstructed layers.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when tracking how data enters, transforms, persists, and exits a system, or when investigating trust boundaries, validation gaps, and potential data exfiltration paths.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when investigating coupling between modules, finding circular dependencies, understanding change impact, or before modifying shared code.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when analyzing, auditing, reverse engineering, or understanding any codebase — especially unfamiliar, inherited, leaked, or complex systems.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
quangphu1912/codebase-analyzer
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code.