when-validating-code-works-use-functionality-auditlisted

# Functionality Audit - Code Execution Validation ## When to Use This Skill **Trigger Conditions:** - After generating new code or modifying existing code - When code appears complete but actual functionality is uncertain - Before merging PRs or deploying to production - When debugging reported issues or unexpected behavior - As part of quality assurance workflows - When validating third-party code integrations **Situations Requiring Functionality Audit:** - Code generated by AI that needs execution validation - Complex logic changes requiring runtime verification - Integration of new libraries or dependencies - Refactoring that may have introduced regressions - Migration to new frameworks or language versions ## Overview This skill systematically validates that code delivers its intended behavior through actual execution rather than static analysis alone. It creates isolated testing environments (sandboxes), executes code with realistic inputs, captures outputs and errors, identifies root causes of failures through systematic debugging, and applies fixes using best practices that preserve existing functionality. The skill emphasizes **genuine functionality over appearance**, detecting "theater code" that looks correct but fails during execution. It combines automated testing, manual validation, and debugging expertise to ensure code reliability. ## Phase 1: Setup Testing Environment (Sequential) **Agents**: tester (lead), coder (support) **Duration**: 10-15 minutes