audit-and-migrate

Audit and migrate technical debt-heavy codebases through phased workflows.

42|11|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/petekp/claude-code-setup --skill audit-and-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-and-migrate
Source: https://github.com/petekp/claude-code-setup/tree/main/skills/audit-and-migrate
Command: npx skills add https://github.com/petekp/claude-code-setup --skill audit-and-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured methodology to audit and migrate codebases burdened by technical debt, preventing common agent failures like drift, vestigial code, and false finishes.

Core Features & Use Cases

  • Phased Approach: Guides users through Audit, Migration, and Closeout phases.
  • CI Ratchets: Enforces migration invariants with automated checks that prevent regression.
  • Anti-Vestigial Discipline: Ensures replaced code is deleted, preventing codebase bloat.
  • Use Case: When tasked with a large refactor or consolidating multiple services, this Skill ensures a controlled, evidence-driven migration with built-in cleanup and a verifiable ship-readiness gate.

Quick Start

Begin the audit phase by creating the migration charter document.

Frequently Asked Questions about audit-and-migrate

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

FAQPage Schema
How do I safely migrate technical debt in a large codebase refactor?

Migrate technical debt safely by using an evidence-driven framework with distinct Audit, Migrate, and Closeout phases. This systematic approach enforces invariants via CI ratchets and prevents vestigial code through strict deletion policies during large refactors.

What are CI ratchets and how do they enforce migration invariants?

CI ratchets are automated checks that enforce migration invariants by preventing regression. They ensure replaced code is deleted and verify migration completion through a defined ship gate, maintaining anti-vestigial discipline throughout the technical debt reduction process.

When do I need a systematic code audit framework for refactoring?

You need a systematic code audit framework when tasked with large refactors, codebase consolidation, or tech debt reduction. It prevents common agent failures like drift, vestigial code, and false finishes by providing a controlled, evidence-driven migration process.

How do I prevent vestigial code during a codebase consolidation?

Prevent vestigial code during consolidation by enforcing strict deletion policies through anti-vestigial discipline. This ensures replaced code is deleted rather than left behind, preventing codebase bloat and maintaining clean migration boundaries.

Does this migration methodology work for large refactors without dependencies?

Yes, this migration methodology works for large refactors with no external dependencies. It implements an advanced systematic framework using scripts and references to guide evidence-driven codebase consolidation and technical debt reduction through verifiable phases.