CLysis
AI-powered framework for understanding, analyzing, and modernizing legacy systems.
Systematic support for investigation, analysis, and modernization of legacy systems using AI agent teams.
11 domain-specific skills and 7 workflow commands across 4 plugins.
Repository Structure
CLysis/
├── .claude-plugin/ # Marketplace manifest
├── agents/ # Agent definitions (karo, metsuke, ashigaru-*)
├── assessment/ # Quality evaluation criteria & maturity model
├── config/ # Terminology customization
├── docs/ # Templates, workflow examples, migration guide
├── legacy-analysis/ # Plugin: change-impact, current-legacy, current-distortion
│ ├── .claude-plugin/
│ ├── commands/
│ ├── examples/
│ └── skills/
├── legacy-execution/ # Plugin: create-pr, review-code
│ ├── .claude-plugin/
│ ├── commands/
│ ├── examples/
│ └── skills/
├── legacy-investigation/ # Plugin: project-guide, current-spec
│ ├── .claude-plugin/
│ ├── commands/
│ ├── examples/
│ └── skills/
├── legacy-knowledge/ # Plugin: doc-organize, current-prd, doc-update, templates
│ ├── .claude-plugin/
│ ├── examples/
│ ├── prompts/
│ └── skills/
├── ARCHITECTURE.md
├── LICENSE
├── README.md
└── validate_plugins.py
Plugins
| Plugin | Skills | Commands | Description |
|---|
| legacy-investigation | 2 | 4 | Investigation & understanding (project-guide, current-spec) |
| legacy-analysis | 3 | 1 | Analysis & planning (change-impact, current-legacy, current-distortion) |
| legacy-execution | 2 | 2 | Execution & review (create-pr, review-code) |
| legacy-knowledge | 4 | 0 | Knowledge accumulation (doc-organize, current-prd, doc-update, templates) |
Prerequisites
- Claude Code — Required
- Serena MCP — Recommended. Enables semantic code search for
/current-spec. Skills work without it but with reduced accuracy.
- GitHub MCP — Optional. Required for
/create-pr and /review-code.
Quick Start
Choose your installation method
- Marketplace (recommended) — Using Claude Code with internet access
- Local — Running locally or in a restricted environment
- Manual — Just want to try individual skills
Installation Methods
Marketplace Installation (Recommended)
Register the marketplace and install plugins:
# Register the marketplace
claude plugin marketplace add t-hasuike/CLysis
# Install individual plugins
claude plugin install legacy-investigation@CLysis
claude plugin install legacy-analysis@CLysis
claude plugin install legacy-execution@CLysis
claude plugin install legacy-knowledge@CLysis
Or install all plugins at once:
# Install all 4 plugins in one command
claude plugin install legacy-investigation@CLysis legacy-analysis@CLysis legacy-execution@CLysis legacy-knowledge@CLysis
# Verify installation
claude plugin list
Local Installation
If running locally or adding to an existing marketplace:
# Add this repository to the marketplace
claude plugin marketplace add CLysis /path/to/CLysis
# Then install plugins as above
claude plugin install legacy-investigation@CLysis legacy-analysis@CLysis legacy-execution@CLysis legacy-knowledge@CLysis
# Verify installation
claude plugin list
Manual Installation
Clone the repository and copy individual skills to your project:
# Clone the repository
git clone https://github.com/t-hasuike/CLysis.git
cd CLysis
# Copy skills from a specific plugin
cp -r legacy-investigation/skills/* /path/to/your/project/.claude/skills/
# Or copy commands
cp -r legacy-investigation/commands/* /path/to/your/project/.claude/commands/
Available Plugins
| Plugin | Skills | Description |
|---|
| legacy-investigation | project-guide, current-spec | Code exploration, service specification, documentation reference |
| legacy-analysis | change-impact, current-legacy, current-distortion | Impact analysis, system overview, code quality patterns |
| legacy-execution | create-pr, review-code | Change proposals and PR creation (--plan/--exec), automated code review |
| legacy-knowledge | doc-organize, current-prd, doc-update, templates | Knowledge extraction, PRD generation, document updates |
Skill Chain Patterns
Common workflows for analyzing and modernizing legacy systems:
Impact Analysis Chain
Investigate the full impact of proposed changes:
/project-guide [your task]
→ /current-spec [target service or area]
→ /change-impact [change description]
Use case: Before implementing a change, understand its ripple effects across the codebase.
Bug Investigation Chain
Locate and understand the root cause of defects: