Production Code Audit
Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations
When to Use
- The request matches the skill description: Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations
- The task needs the implementation patterns, examples, validation checks, or edge cases listed in the topic map.
- The work would benefit from the complete guidance preserved in
references/full-guidance.md.
Core Workflow
- Confirm the request matches this skill's trigger, scope, and risk profile.
- Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
- Load
references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
- Apply only the relevant guidance instead of loading or repeating the entire reference by default.
- Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.
Topic Map
- Overview
- When to Use This Skill
- How It Works
- Step 1: Autonomous Codebase Discovery
- Step 2: Comprehensive Issue Detection
- Step 3: Automatic Fixes and Optimizations
- Step 4: Verify and Report
- Examples
- Example 1: Autonomous Codebase Transformation
- Example 2: Automatic Security Hardening
- Example 3: Performance Optimization
- Best Practices
- ✅ Do This
- ❌ Don't Do This
- Autonomous Scanning Instructions
- Common Pitfalls
- Problem: Too Many Issues
- Problem: False Positives
Reference Map
references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Progressive Loading
Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.
1---2name: production-code-audit3description: Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations4license: MIT5---67# Production Code Audit89Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations1011## When to Use12- The request matches the skill description: Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations13- The task needs the implementation patterns, examples, validation checks, or edge cases listed in the topic map.14- The work would benefit from the complete guidance preserved in `references/full-guidance.md`.1516## Core Workflow171. Confirm the request matches this skill's trigger, scope, and risk profile.182. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.193. Load `references/full-guidance.md` when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.204. Apply only the relevant guidance instead of loading or repeating the entire reference by default.215. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.2223## Topic Map24- Overview25- When to Use This Skill26- How It Works27- Step 1: Autonomous Codebase Discovery28- Step 2: Comprehensive Issue Detection29- Step 3: Automatic Fixes and Optimizations30- Step 4: Verify and Report31- Examples32- Example 1: Autonomous Codebase Transformation33- Example 2: Automatic Security Hardening34- Example 3: Performance Optimization35- Best Practices36- ✅ Do This37- ❌ Don't Do This38- Autonomous Scanning Instructions39- Common Pitfalls40- Problem: Too Many Issues41- Problem: False Positives4243## Reference Map44- `references/full-guidance.md` preserves the complete original guidance, including examples and detailed edge cases.4546## Limitations47- Use this skill only when the task clearly matches the scope described above.48- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.49- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.5051## Progressive Loading52Keep this `SKILL.md` as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.