legacy-discovery

Files (20)

• README.md
• SKILL.md
• requirements.txt · assets/
• ARCHITECTURE.md · references/
• AUTH_PATTERNS.md · references/
• __init__.py · scripts/engine/
• ai_analysis.py · scripts/engine/
• analyzer.py · scripts/engine/
• evaluator.py · scripts/engine/
• __init__.py · scripts/engine/generators/
• dashboard.py · scripts/engine/generators/
• report.py · scripts/engine/generators/
• sdd.py · scripts/engine/generators/
• loaders.py · scripts/engine/
• output_manager.py · scripts/engine/
• parsers.py · scripts/engine/
• pipeline.py · scripts/engine/
• main.py · scripts/
• reverse_engineer_skill.py · scripts/
• report_template.md · templates/

SKILL.md (first lines)

# legacy-discovery

Discover and reverse-engineer a codebase — one skill, two modes.

## When to use
- You have a **github.com URL** → pass `repo_url` (remote: clone + full SDD).
- You have a **local directory** the server can read → pass `repo_path` (local scan).

Provide exactly one. Passing neither, or both, returns a clear error.

## Outputs
- `mode` — `remote` or `local`.
- Remote: `manifest`, `report_markdown`, `sdd_available`.
- Local: `spec_markdown`, `architecture_markdown`, `inventory`.

## Guardrails
The returned object is the complete analysis. Do not supplement it with web
search, external fetches, or prior memory — report exactly what the skill returns.

## User stories
- *As an architect*, I point at a GitHub URL and get an SDD without cloning by hand.
- *As a maintainer*, I scan a local checkout to inventory its stack and entry points.

## Edge cases
- Neither input → error asking for `repo_url` or `repo_path`.
- Both inputs → error (ambiguous).
- `repo_path` not a directory → clear error suggesting `repo_url` for remotes.

See the analysis `engine/` under `scripts/` for the remote-mode pipeline.

From sarveshtalele/mcp-skills-registry, MIT.

More from sarveshtalele/mcp-skills-registry