Produces comprehensive summaries and insights about legacy codebases to help understand unfamiliar code. Use when onboarding to a new project, planning refactoring efforts, assessing code for acquisition/migration, or generating documentation for undocumented systems. Analyzes architecture, dependencies, code quality issues, and test coverage. Creates high-level overviews with architecture diagrams, key components, entry points, and actionable insights for understanding and improving legacy code.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill legacy-code-summarizer79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Full legacy codebase summary report
Executive Summary present
85%
100%
Key Metrics block
80%
80%
Architecture Overview section
100%
100%
ASCII architecture diagram
44%
100%
Architecture pattern identified
100%
100%
Dependency map format
55%
55%
Entry Points section
100%
100%
Code Quality section
100%
100%
Test Coverage section
100%
100%
Three-timeframe recommendations
70%
100%
Quick Reference section
100%
100%
Specific file references
100%
100%
Without context: $0.2226 · 1m 45s · 9 turns · 14 in / 4,021 out tokens
With context: $0.6341 · 2m 52s · 14 turns · 7,046 in / 6,601 out tokens
Code quality audit with severity prioritization
Severity categorization
100%
100%
File size thresholds
0%
0%
Function length threshold
0%
0%
Hardcoded credentials identified
100%
100%
SQL injection detected
100%
100%
Silent exception handling
100%
100%
Magic numbers identified
100%
100%
Code duplication identified
100%
100%
TODO/FIXME/HACK count
62%
100%
Test coverage target stated
0%
100%
Specific file/line references
100%
100%
Security issues classified Critical
100%
100%
Without context: $0.5055 · 3m 10s · 20 turns · 26 in / 8,745 out tokens
With context: $0.8188 · 3m 38s · 23 turns · 6,604 in / 9,625 out tokens
Architecture and dependency mapping
Architecture pattern named
80%
100%
Architecture template used
70%
70%
ASCII architecture diagram
100%
100%
Dependency map format
41%
100%
Circular dependency detected
100%
100%
Circular dep resolution strategy
100%
100%
Highly coupled modules flagged
75%
100%
External vs internal deps distinguished
37%
62%
File paths in dependency map
100%
100%
Microservice extraction candidates
100%
100%
Without context: $0.2041 · 1m 44s · 8 turns · 13 in / 4,370 out tokens
With context: $0.5185 · 1m 48s · 14 turns · 5,146 in / 5,678 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.