Skip to content

a5c-ai/babysitter / library/specializations/code-migration-modernization/skills/legacy-code-interpreter

legacy-code-interpreter

Verified

Understand and document legacy code behavior through deep analysis and behavior characterization

FileKindSize
README.mdmarkdown1.5 KB
SKILL.mdskill md2.9 KB
---
name: legacy-code-interpreter
description: Understand and document legacy code behavior through deep analysis and behavior characterization
allowed-tools: ["Bash", "Read", "Write", "Grep", "Glob", "Edit"]
graph:
  domains: [domain:software-engineering]
  specializations: [specialization:code-migration-modernization]
  skillAreas: [skill-area:code-analysis-linting, skill-area:dead-code-elimination]
  roles: [role:backend-engineer, role:architect]
  workflows: [workflow:technical-debt-reduction]
  topics: [topic:refactoring]
---

# Legacy Code Interpreter Skill

Deep analysis and interpretation of legacy code to understand undocumented behavior, extract business logic, and characterize system functionality.

## Purpose

Enable legacy code understanding for:
- Business logic extraction
- Undocumented feature discovery
- Behavior characterization
- Migration planning
- Knowledge preservation

## Capabilities

### 1. Business Logic Extraction
- Parse conditional logic
- Extract calculation formulas
- Identify validation rules
- Document decision trees

### 2. Undocumented Feature Discovery
- Find hidden functionality
- Identify feature flags
- Discover Easter eggs
- Map admin features

### 3. Control Flow Analysis
- Trace execution paths
- Map state machines
- Identify loops and recursion
- Document entry points

### 4. Data Flow Tracking
- Trace data transformations
- Map input to output
- Identify side effects
- Document state changes

### 5. Side Effect Identification
- Find external calls
- Identify I/O operations
- Map database operations
- Document messaging

### 6. Behavior Characterization
- Create behavior summaries
- Generate pseudo-code
- Document edge cases
- Map error handling

## Tool Integrations

| Tool | Purpose | Integration Method |
|------|---------|-------------------|
| Understand (SciTools) | Deep analysis | CLI / API |
| Lattix | Architecture analysis | CLI |
| CodeScene | Behavioral analysis | API |
| Sourcetrail | Code exploration | CLI |
| ast-grep | Pattern matching | MCP / CLI |

## Output Schema

```json
{
  "analysisId": "string",
  "timestamp": "ISO8601",
  "interpretation": {
    "businessLogic": [
      {
        "name": "string",
        "location": "string",
        "description": "string",
        "pseudoCode": "string",
        "inputs": [],
        "outputs": [],
        "sideEffects": []
      }
    ],
    "controlFlow": {
      "entryPoints": [],
      "stateMachines": [],
      "criticalPaths": []
    },
    "dataFlow": {
      "transformations": [],
      "stateChanges": []
    },
    "undocumented": []
  }
}
```

## Integration with Migration Processes

- **legacy-codebase-assessment**: Primary interpretation tool
- **migration-planning-roadmap**: Knowledge source

## Related Skills

- `static-code-analyzer`: Structural analysis
- `knowledge-extractor`: Documentation mining

## Related Agents

- `legacy-system-archaeologist`: Uses for excavation
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall