One-click install
npx skills add https://github.com/outfitter-dev/outfitter --skill migration-outfitter-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration
Source: https://github.com/outfitter-dev/outfitter/tree/main/packages/claude-plugin/skills/migration
Command: npx skills add https://github.com/outfitter-dev/outfitter --skill migration-outfitter-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @outfitter/contracts, @outfitter/logging, @outfitter/config, @outfitter/cli, @outfitter/mcp, @outfitter/file-ops, @outfitter/daemon, @outfitter/testing, and includes scripts (resource) and references (resource) and templates (resource) components.

What problem does it solve?

This Skill automates the process of migrating existing codebases to adopt modern, robust patterns like Result-based error handling, structured logging, and standardized path management, significantly reducing manual effort and potential errors.

Core Features & Use Cases

  • Code Auditing: Scans your project for common anti-patterns such as throw statements, console.log, and hardcoded paths.
  • Automated Plan Generation: Creates a detailed, stage-by-stage migration plan with actionable tasks and estimated effort.
  • Pattern Conversion: Provides guidance and examples for converting exceptions to Result types, console to structured logging, and hardcoded paths to XDG conventions.
  • Use Case: You're adopting the Outfitter Stack for a legacy Node.js project. Run this Skill to get a clear roadmap for refactoring error handling, logging, and file path management to align with the new stack's best practices.

Quick Start

Run the scanner to generate a migration plan for your current project.

Frequently Asked Questions about migration

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

FAQPage Schema
How do I migrate a Node.js codebase to use Result types instead of exceptions?

To migrate exceptions to Result types, this Skill audits your codebase for throw statements and generates a structured migration plan with actionable tasks and examples for converting to Result-based error handling.

What is the best way to replace console.log with structured logging during code modernization?

Replacing console.log with structured logging is automated by scanning your project for console statements, generating audit reports, and providing stage-specific guidance to adopt standardized logging patterns.

How do I convert hardcoded file paths to XDG conventions when refactoring?

Converting hardcoded paths to XDG conventions is handled by auditing your existing code for path anti-patterns and generating a detailed migration plan with actionable tasks to standardize path management.

Can I get an estimated effort breakdown for refactoring a legacy project to the Outfitter Stack?

Yes, you can get an estimated effort breakdown by running the scanner, which generates a stage-by-stage migration plan complete with actionable tasks and estimated effort for each phase.

Does the migration Skill work with existing Node.js projects that use hardcoded paths and console logging?

Yes, it works with existing Node.js projects by auditing for common anti-patterns like throw statements, console.log, and hardcoded paths, then generating a roadmap to align with Outfitter Stack best practices.