# Nuke Recon

> Use when a repo needs mapping before real work — "nuke recon", "map this repo", "get familiar with the codebase", first session in an unfamiliar project — or when other nuke skills keep re-scanning because .nuke/repo-map.md is missing or stale. Builds the shared repo map once; every ceremony consumes it for free afterwards.

- Skill: `b4r7x/nuke-recon` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add b4r7x/nuke-recon`
- Raw SKILL.md: https://api.skillmd.com/api/skills/b4r7x/nuke-recon/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: b4r7x (https://skillmd.com/u/b4r7x)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/b4r7x/nuke-recon

---


# Nuke Recon

A small helper, not a ceremony (map: references/family-map.md): 0–1 agents, no preflight confirmation, no run_dir. It does one thing — build or refresh `.nuke/repo-map.md`, the durable recon cache the ceremonies otherwise produce as an audit by-product. Run it once in a new repo and every later nuke run starts warm.

## Protocol

One clerk-tier scout (references/model-tiers.md) — or the orchestrator directly when spawning is unavailable — produces, per the recon rules the ceremonies share:

1. **Stack**: manifests, languages, frameworks, workspace layout.
2. **Conventions**: project instruction files (CLAUDE.md, AGENTS.md, .cursorrules, copilot-instructions) distilled — these define what is *intentional*.
3. **Gates**: the per-path-prefix gates table per references/stack-adapters.md (test · typecheck · lint), resolved verbatim from manifest scripts → CI → fallback table; gateless areas flagged.
4. **Architecture sketch**: top-level areas, entry points, the import direction between layers — one screen, not an essay.
5. **File-type → skill map**: local skill library listed once, matched per references/stack-adapters.md.
6. **Security surfaces** detected per the same file (web / CLI / library / daemon / infra / ai).

Stamp the map with date + HEAD. `--refresh` (or an existing stale map): verify against git history since the stamp and update deltas — never re-scan what did not change.

## Mandates

- Read-only on the codebase; the only write is `.nuke/repo-map.md`. No git commands.
- The map records durable facts, never run-specific scope or findings — those belong to ceremony run dirs.
- Honest gaps: an area recon could not classify is marked `unmapped`, not guessed.

## Hand-back

Five lines or fewer: stack one-liner · gate rows count (+ gateless areas) · surfaces detected · skill-map matches · the map's path. Everything else lives in the map.