seam-ripper

Analyze architectural seams and map dependencies to surface coupling problems.

5|2|Updated Jan 20, 2026

Search Tags:#architecture #interfaces #codebase #dependencies #refactor #analyze

Ready to run

npx skills add https://github.com/petekp/agent-skills --skill seam-ripper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: seam-ripper
Source: https://github.com/petekp/agent-skills/tree/main/skills/seam-ripper
Command: npx skills add https://github.com/petekp/agent-skills --skill seam-ripper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ruthlessly analyze architectural seams—the interfaces, boundaries, and contracts between system components—to expose coupling problems, abstraction leaks, and design failures. Use when asked to review architecture, analyze coupling, find interface problems, improve module boundaries, audit dependencies, or redesign system structure. Produces uncompromising redesign proposals that prioritize correctness over backwards compatibility.

Core Features & Use Cases

Comprehensive boundary mapping across modules and packages
Identify interface contracts, data flows, and dependency direction
Propose actionable redesigns with concrete steps and migration plan

Quick Start

Request a seam-ripper analysis by providing the system's architecture or a codebase segment.

Frequently Asked Questions about seam-ripper

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

FAQPage Schema

How do I analyze architectural seams and boundaries in a codebase?▼

Mapping dependencies, interfaces, and data contracts across modules reveals architectural coupling problems and design flaws. This analysis exposes abstraction leaks and produces a structured transformation plan with actionable redesign recommendations.

What is the best way to find interface coupling problems in my software architecture?▼

Finding interface coupling problems requires auditing module boundaries and dependency directions to expose abstraction leaks. This identifies where contracts are violated and produces uncompromising redesign proposals that prioritize correctness over backwards compatibility.

How do I redesign module boundaries to fix abstraction leaks?▼

Redesigning module boundaries requires mapping dependency directions and data flows to identify abstraction leaks. This produces a structured transformation plan with concrete migration steps, prioritizing architectural correctness over backwards compatibility to resolve design failures.

Can I audit dependencies and data contracts across multiple modules?▼

Auditing dependencies and data contracts across modules is supported by mapping interface boundaries and data flows. This comprehensive boundary mapping exposes design flaws and coupling problems, generating an evidence-based redesign plan with actionable recommendations.

When should I not prioritize backwards compatibility during a system refactor?▼

When resolving architectural coupling problems and abstraction leaks, prioritizing correctness over backwards compatibility is recommended. This approach ensures uncompromising redesign proposals that properly fix design failures rather than preserving flawed boundaries.

Does this architectural analysis work with any codebase segment?▼

Yes, providing the system's architecture or a codebase segment is sufficient for analysis. The process maps dependencies, interfaces, and data contracts to surface coupling problems and generate a structured transformation plan with concrete steps.