migrate-to-earl

What problem does it solve?

This Skill automates the tedious and risky process of replacing raw CLI and HTTP API invocations spread across a codebase with reviewed, reusable Earl templates, reducing accidental secret leakage and making call sites reviewable and reversible.

Core Features & Use Cases

• Repository-wide scanning: Grep-based detection across scripts, CI workflows, Dockerfiles, and common source files using a maintained mapping of CLI and URL patterns.
• Template import or creation: Import pre-built provider templates when available or invoke create-template for unmatched commands, including secret setup and validation.
• Safe, staged rewrites: Map call sites to Earl commands, run test calls, pause for a commit checkpoint, rewrite up to ten call sites per provider, and flag complex pipelines for manual review.
• Use case: Migrate GitHub curl/gh calls or Stripe CLI usages in a project to Earl templates one provider at a time to keep changes small and auditable.

Quick Start

Ask the skill to scan the repository for provider patterns, import or create the provider template, set required secrets, verify commands, and then rewrite up to ten approved call sites.