repo-surgeon

Audit repositories with a five-pass process and generate repair plans.

Updated May 22, 2026
One-click install
npx skills add https://github.com/asifhussain60/journal --skill repo-surgeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-surgeon
Source: https://github.com/asifhussain60/journal/tree/main/skills-staging/repo-surgeon
Command: npx skills add https://github.com/asifhussain60/journal --skill repo-surgeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Holistic repo governance by surfacing structural drift, root clutter, orphaned files, and architectural deviations, enabling targeted repairs.

Core Features & Use Cases

  • Five-pass audit (Structure, Code, Architecture, Brittleness, Plan Conformance) to identify issues and assemble a repair plan.
  • Generates a repair-and-execute plan that can be approved before applying changes, updating registries and prompts as needed.
  • Produces per-pass reports, enforces governance, and maintains a run log for traceability.

Quick Start

Trigger the repo-surgeon to run a five-pass audit on your repository and generate a repair plan for review.

Frequently Asked Questions about repo-surgeon

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

FAQPage Schema
How do I identify root clutter and architectural drift in my repository?

A repository structural audit surfaces root clutter, dead code, and architectural deviations by performing a five-pass analysis that inspects structure, code, architecture, brittleness, and plan conformance to generate a repair plan.

What is the best way to automate repository governance and maintain traceability?

Automating repository governance enforces traceability by exporting per-pass audit reports and maintaining a run log, ensuring all structural repairs and registry updates are fully documented.

How do I generate a repair plan for dead code and orphaned files without breaking my codebase?

Generating a repair plan for dead code involves assembling issues from the audit passes into a repair-and-execute plan that requires your explicit approval before applying any fixes or updating registries.

Does this repository audit tool require any external dependencies to run a code review?

No external dependencies are required to run this architectural code review, as the five-pass audit operates independently to surface brittleness and plan conformance issues for your repository.

When do I need a five-pass repository audit instead of a standard code review?

You need a five-pass repository audit when a standard code review is insufficient to detect holistic structural drift, root clutter, and architectural brittleness affecting overall repo health.