reverse-engineering-toolkit
Understand undocumented systems through static/dynamic analysis, dependency mapping, and pattern recognition
Profile →npx skills add majiayu000/claude-skill-registry --skill reverse-engineering-toolkit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Reverse Engineering Toolkit ## Purpose This skill enables you to understand systems without documentation by analyzing code structure, runtime behavior, dependencies, and design patterns. Use this when facing: - Undocumented legacy codebases requiring modernization - Third-party APIs with incomplete specifications - Lost or outdated design documentation - Security audits of closed-source systems - Onboarding to unfamiliar codebases ## When to Use This Skill **Use reverse engineering when**: - Documentation is missing, outdated, or incomplete - System behavior needs to be understood through observation - Dependencies and coupling need to be visualized - Design patterns need to be identified and cataloged - API contracts need to be inferred from implementation - Legacy code requires understanding before refactoring **Do NOT use when**: - Good documentation already exists (read it instead!) - Source code is unavailable (different techniques needed) - Simple codebase can be understood by reading - Time constraints don't allow deep analysis ## Quick Start: 4-Step Process ### 1. Discover Identify what exists in the system: ```bash # Find all source files find . -type f -name "*.py" -o
- Purpose
- When to Use This Skill
- Quick Start: 4-Step Process
- 1. Discover
- 2. Map
- 3. Analyze
- 4. Document
- Core Patterns Overview
- Pattern 1: Static Code Analysis
- Pattern 2: Dynamic Analysis & Tracing
- Pattern 3: Dependency Graph Extraction
- Pattern 4: Design Pattern Recognition
- Pattern 5: Documentation Generation
- Detailed Resources
Find all source files find . -type f -name "*.py" -o -name "*.js" -o -name "*.java" Count lines of code cloc . Identify entry points grep -r "main\|app\|server" --include="*.py" Trace execution strace -o trace.log ./program Analyze function calls python -m pycallgraph graphviz -- ./script.py
What does the reverse-engineering-toolkit skill do?
Understand undocumented systems through static/dynamic analysis, dependency mapping, and pattern recognition
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill reverse-engineering-toolkit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.