Ingeniería
Map the legacy repo before the agent edits a line
Agents love to skim old repos — that is where the guesses hide.
Qué dolía
klöss (@kloss_xyz) shared a paste-before-you-edit prompt for Opus, Astra, or Grok Bot on legacy code: map the codebase, trace what the task will touch, flag dead code and hidden side effects, and make no edits until you approve the map. Not affiliated with xAI.
Qué instalar o crear
Paste his quoted prompt as the first message before any edit session. Approve the map, then allow edits.
Bots
Legacy coder
Maps first. Edits only after you approve the map.
Plugins
GitHub
Opcional
Rutinas
Ninguna en el primer uso. Mira primero una pasada manual.
El prompt
Map before edit (author-quoted)
Quoted from @kloss_xyz — as published. Do not invent a second system prompt.
Before we change anything, map this entire codebase. Trace every piece of code this task and session will touch, what depends on it, and what breaks if it changes. Flag any dead code, hidden side effects, and literally anything you're guessing about that's not proven by code reads and specific lines. No code edits until I approve the map manually.
Primer uso
- 1Read https://x.com/kloss_xyz/status/2109747284044824692 (credit @kloss_xyz).
- 2Open the legacy repo with your coding bot.
- 3Paste his map prompt as the first message — before any edit.
- 4Review the map: dependencies, break risks, guesses vs proven lines.
- 5Approve the map, then allow the bot to edit.
Valla de aprobación
Do not merge or deploy without your yes after the map.
Qué ajustar
Steal the map-then-approve gate. No code edits until the map is proven.
Fuente
klöss @kloss_xyz · Publicación original
Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.
Paquete Pro
¿Quieres la configuración completa, no solo la idea?
Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.