shipshape

Orchestrate end-to-end refactoring campaigns with baselining, gated tasks, and scorecard reviews.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/api-haus/my-claude-workflow --skill shipshape
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipshape
Source: https://github.com/api-haus/my-claude-workflow/tree/main/skills/shipshape
Command: npx skills add https://github.com/api-haus/my-claude-workflow --skill shipshape

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates end-to-end, publish-grade refactoring campaigns for code packages, turning chaotic changes into a structured, auditable process.

Core Features & Use Cases

  • Baseline and survey phases to identify structural issues and risks.
  • A queue-driven workflow that slices work into small, auditable commits.
  • An adversarial review pass and a final scorecard to validate readiness for release.
  • Optional automation of gates and metrics collection to reduce manual toil.

Quick Start

Run shipshape on a target package to baseline, survey, and execute a gated refactor pass.

Frequently Asked Questions about shipshape

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

FAQPage Schema
How do I orchestrate a large-scale code refactoring campaign without breaking existing functionality?

Refactoring orchestration structures large-scale code changes into a gated queue of small, auditable commits. It baselines the target package, surveys for structural issues, and drives a sequential workflow to ensure high-quality outcomes.

What is a gated refactoring workflow and how does it improve code quality?

A gated refactoring workflow slices code changes into single-dispatch items that must pass checks before proceeding. This queue-driven process enforces metrics collection and uses adversarial review to validate readiness and improve code quality.

How do I generate a code quality scorecard before and after a refactor?

You generate a before/after code quality scorecard by baselining the target package, executing queued refactoring tasks, and collecting metrics throughout the process. The final scorecard validates structural improvements and release readiness.

Can I use automated metrics collection to reduce manual toil during package refactoring?

Yes, automated metrics collection and gate enforcement reduce manual toil during package refactoring. The orchestration process automatically collects metrics at each gated step to ensure auditable, high-quality refactoring outcomes.

What is the best way to validate code readiness for release after structural changes?

The best way to validate release readiness is an adversarial review pass combined with a final scorecard. This evaluates the collected metrics against the baseline to ensure the refactored package meets publish-grade standards.