By cliftonc
Reverse engineer unfamiliar codebases by running unwind:start to orchestrate layer-by-layer analysis from database schemas and domain models to services, APIs, frontend routes, messaging, and tests, generating structured Markdown docs in docs/unwind/layers/, detecting gaps in coverage, and producing architecture summaries plus rebuild plans.
npx claudepluginhub cliftonc/unwindUse when analyzing REST/GraphQL API endpoints, contracts, authentication, and client-facing interfaces
Use when analyzing the database layer including schema, migrations, ORM configuration, and data access patterns
Use when analyzing domain entities, value objects, aggregates, and business rules encoded in the model
Use when analyzing end-to-end tests including browser automation, API workflows, and full system testing
Use when analyzing frontend/UI layer including components, state management, routing, and API integration (optional - skip if no frontend exists)
Use when analyzing integration tests that verify component interactions, database access, and external service integration
Use when analyzing event-driven systems, message queues, async processing, and pub/sub patterns
Use when analyzing business logic, use cases, service orchestration, and data transformation including DTOs and mappers
Use when analyzing unit test coverage, patterns, and test code for isolated component testing
Use after verifying-layer-documentation to fix all gaps found. Reads gaps.md and adds missing documentation.
Use when starting reverse engineering on an unfamiliar codebase to identify layers, patterns, and structure before detailed analysis
Use after layer analysis is complete to validate architecture documentation and generate a strategic rebuild plan focused on re-use decisions
Use after unwind:start to orchestrate layer-by-layer analysis using specialist subagents
Use when starting any reverse engineering task - establishes how to find and use Unwind skills for codebase analysis, service mapping, and documentation
Use after layer analysis to detect gaps in documentation. Outputs a work list for completing-layer-documentation.
Use this agent when you need to analyze a service or codebase component and create comprehensive documentation in CLAUDE.md files. This agent should be invoked after implementing new services, major refactoring, or when documentation needs updating to reflect the current codebase structure. Examples: <example>Context: The user has just implemented a new authentication service and wants to document it properly. user: 'I just finished implementing the auth service, can you document how it works?' assistant: 'I'll use the codebase-documenter agent to analyze the authentication service and create detailed documentation in CLAUDE.md' <commentary>Since the user has completed a service implementation and needs documentation, use the Task tool to launch the codebase-documenter agent to create comprehensive CLAUDE.md documentation.</commentary></example> <example>Context: The user wants to ensure a newly added API module is properly documented for the team. user: 'We need documentation for the new payment processing API I just added' assistant: 'Let me use the codebase-documenter agent to analyze the payment processing API and create proper documentation' <commentary>The user needs documentation for a new API module, so use the codebase-documenter agent to create CLAUDE.md files with setup instructions and architectural notes.</commentary></example>
AI-powered codebase understanding assistant. Learn design patterns, analyze impact, trace code flows, and understand any codebase through information theory principles. Includes 6 Agent Skills for automatic analysis triggering.
Helps Claude read a planning document and explore related files to get familiar with a topic. Asking Claude to prepare to discuss seems to work better than asking it to prepare to do specific work. This is followed by Plan, then Execute.
Share bugs, ideas, or general feedback.
Codebase exploration, refactoring, and quality analysis
Architecture analysis, brainstorming, 12-Factor compliance, ADR generation, and LLM-as-judge comparison.
Smart codebase exploration with dependency mapping and structure analysis
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim