repo-reconnaissance
Performs a fast, read-only structural survey of a repository, monorepo, or multi-repo estate before a migration, replatform, or due-diligence assessment. Use as the reconnaissance phase of legacy-code-discovery, or standalone when you need to inventory a codebase for migration scope: which stacks and versions it uses, how it builds, tests, and deploys, which deployable units exist, what should be excluded, how to split a large repository into workable analysis shards, or how to emit a project profile. Prefer legacy-code-discovery when the request spans more than one phase or needs a durable bundle. Produces a repository registry, stack map, coverage ledger, and, when requested, .sdlc/profile.json. Not for everyday code exploration, feature work, or behavior analysis.
- Compatibility
- Requires read access to the target repositories and write access to the discovery bundle and, when requested, the repository's .sdlc/profile.json. Designed to be used with legacy-code-discovery, system-cartography, and migration-seams from the same plugin.
Pinned to revision fb8a98322630, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/repo-reconnaissance/SKILL.md
- skills/repo-reconnaissance/references/commands.md
- skills/repo-reconnaissance/references/detection.md
- skills/repo-reconnaissance/references/profile.md
Every link opens the file at its source, pinned to the revision this page describes.