project-surgeon-lite

Codebase takeover involves scanning and reviewing an existing project to understand its structure, then executing a controlled improvement workflow. This two-phase process targets security, logic, and error handling gaps while preserving working functionality.

Plan refactoring tasks by capturing a test baseline, then applying a preservation gate that re-runs detected test commands after each task. This prevents pass-count decreases and ensures stability while you apply security hardening and error handling improvements.

Yes, this lightweight workflow is specifically designed for fast two-phase runs and works well with smaller models. It separates the read-only Understand phase from the Execute phase to maintain control and minimize regressions during quality upgrades.

The best way to upgrade an inherited project for production readiness is to run a controlled workflow that targets security issues, logic problems, and error handling gaps. This emphasizes observability, security hardening, and resilience while avoiding regressions.

Yes, the codebase improvement workflow requires user-approval gates before execution. After the initial read-only Understand phase analyzes the project, you must explicitly approve the findings before the Execute phase begins applying improvements.