stack-audit_skill

Overview

This skill scans a TypeScript codebase to find Outfitter Stack adoption candidates and produces a structured audit report. It detects throw statements, try/catch usage, console logging, hardcoded paths, and custom error classes to assess readiness and scope for migration.

How this skill works

The scanner searches the project for patterns like throw expressions, try/catch blocks, console.* calls, homedir/tilde paths, and class declarations extending Error. It generates an .outfitter/adopt/ directory containing audit-report.md and a stage-by-stage plan that maps findings to migration tasks and priorities.

When to use it

• Before planning Outfitter Stack adoption to assess scope and risk.
• When evaluating how much code needs conversion from throws to Result patterns.
• To find logging and path issues that block secure, cross-platform migrations.
• When estimating effort and prioritizing migration stages.
• During code health checks to surface custom errors and complex error-handling hotspots.

Best practices

• Run the scanner for large projects to produce a machine-readable report and plan.
• Review unknowns manually; complex patterns often need human judgment.
• Prioritize Foundation stage tasks (context/logger) before rewrites of handlers.
• Use effort estimation buckets (0, 1–5, 6–15, 16+) to plan sprints.
• Convert console logging to structured logging as part of early foundation work.

Example use cases

• Generate an adoption audit to estimate time and staffing for a migration.
• Locate functions with multiple throw statements to target for Result conversion.
• Find and replace hardcoded home-directory paths with XDG-compliant paths.
• Identify frequently used custom error classes to map to the Outfitter taxonomy.
• Produce an actionable plan directory with staged tasks for incremental migration.