project-surgeon-lite

Name: project-surgeon-lite
Availability: InStock
Author: Obsidian

Analyzes then refactors an existing codebase with user-approved, test-verified steps.

65|8|Updated Apr 2, 2026

Search Tags:#code review #refactoring #error handling #task planning #security hardening #test preservation #project takeover

Ready to run

npx skills add https://github.com/EasyCode-Obsidian/workflow-architect --skill project-surgeon-lite

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-surgeon-lite
Source: https://github.com/EasyCode-Obsidian/workflow-architect/tree/main/claude/skills/project-surgeon-lite
Command: npx skills add https://github.com/EasyCode-Obsidian/workflow-architect --skill project-surgeon-lite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It helps you take over an existing codebase safely by performing a read-only analysis first, then executing a prioritized set of improvements without breaking working functionality.

Core Features & Use Cases

Codebase takeover (2-phase runtime): Understand the project via scanning and structured review, then execute an improvement plan.
Production-readiness improvements: Targets security issues, logic problems, error handling gaps, and consistency issues, emphasizing observability, security hardening, and resilience.
Preservation Gate: Captures a test baseline and runs tests after each code-changing task to prevent regressions.

Quick Start

Use it to take over the repository at the current folder by invoking the skill with the argument project_path set to "." and then approve the Understand findings to start Execute.

Frequently Asked Questions about project-surgeon-lite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely take over and refactor an existing codebase without breaking functionality?▼

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.

How do I plan code refactoring tasks to avoid introducing regressions?▼

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.

Can I use this codebase takeover workflow for fast runs with smaller models?▼

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.

What is the best way to upgrade an inherited project for production readiness?▼

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.

Do I need to approve changes before the codebase improvement workflow executes?▼

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.