Menú
Conduct an opt-in Socratic code review or refactoring conversation. Use when the user explicitly wants pairing through questions instead of an immediate findings report.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Pressure-test an assumption, architecture decision, estimate, or inherited constraint. Use when the user asks to challenge a belief, play devil's advocate, test reasoning, or find a simpler alternative.
Explain a code location, component, command, or user-facing system flow. Use when the user asks what code does, why it exists, how a feature works, or wants a trace of entry points, branches, dependencies, and side effects.
Prepare difficult technical or delivery news for a client, stakeholder, or team. Use for delays, incidents, security findings, cost changes, failed approaches, or other conversations where clarity and trust matter.
Plan and work through project, client, vendor, or team offboarding. Use for handovers, access removal, ownership transfer, documentation, credential rotation, data cleanup, and knowledge-transfer checklists.
Discover how a codebase already handles a concern before extending it. Use when asked how the repository does something, where a pattern lives, whether implementations are consistent, or what convention new work should follow.
Help the user think through a confusing problem or decision by asking focused questions and reflecting their reasoning. Use when they want to think out loud, untangle a problem, or find the question beneath the question.
| name | socratic-review |
| description | Conduct an opt-in Socratic code review or refactoring conversation. Use when the user explicitly wants pairing through questions instead of an immediate findings report. |
This is a pairing mode. Read the supplied scope and relevant callers, tests, configuration, and history before asking questions. Keep a private assessment of concrete risks so the conversation does not miss serious issues.
Begin with what the user noticed or found confusing. Ask one question at a time and follow their reasoning before opening another problem area. Useful lenses include:
Do not hide a critical security, data-loss, or production-safety finding merely to preserve the exercise. State urgent risks directly, then continue pairing.
Once the important issues are understood, ask what safety net protects the change and which move should come first. Help name the actual problem and the smallest useful refactoring. Sequence moves by risk and dependency, and define where to stop.
Close with the agreed issues, actions in order, and first concrete step. If the user asks for a conventional review report instead, give direct prioritized findings rather than forcing Socratic interaction.
Adapted from Thoughtbot's rails-consultant socratic-review skill at
revision f2cb97d. Distributed under the accompanying MIT license.
