Code Repair Spine

High-Integrity Repository Auditing & Handoff

The Code Repair Spine (CRS) is a developer-centric audit tool designed to bridge the gap between discovery and execution. It generates a comprehensive, read-only Phase 1 bundle for local repositories, providing the evidence-backed planning needed before starting a repair or build pass. Unlike simple LLM prompts, this skill executes a multi-step workflow including dependency graphing, secret scanning, and risk assessment to build a structured context for any AI agent.

What it does

• Deep Inventory: Scans local repos to generate Python and JS/TS dependency graphs and repository maps.
• Secret Safety: Conducts secret scanning with mandatory redaction and salted fingerprints, so raw secret values don't enter your LLM context.
• Actionable Planning: Produces a "Break Plan," "Map of Change," and specific prompts (GPT/Codex/Claude/Hardening) tailored to the codebase.
• Read-Only Operation: Operates strictly in read-only mode against the target repo, and blocks any run whose output directory resolves inside that repo.

Why use this skill

Prompting an AI to "fix my code" often leads to hallucinations or missed architectural constraints. CRS provides a standardized "Spine"—a structured set of artifacts that ground the AI in reality. It automates the tedious work of repo mapping and risk analysis, delivering a handoff bundle that serves as a single source of truth for subsequent development phases.

Important boundary

This is not an auto-fixer, security certificate, compliance review, or production-readiness certificate. It does not claim that all secrets or all vulnerabilities were found, or that the repository is safe to deploy. It is a local, evidence-bound repo review and handoff tool for authorized repositories.