CommandValidated

Explain-before-accept — keep comprehension with acceptance

An /explain slash command (rule form for Cursor/Codex): what the change does, why this approach, what could break, and the one thing to verify yourself — before you accept it.

$cosq add explain-before-accept

Free, works signed out. No CLI? Copy the file below into your repo — same result.

Why this one

Passive acceptance lowered comprehension while engaged interaction preserved skill (Anthropic skill-formation study), so make explanations a habit.

How to use it

  1. 1Ask for an explanation before accepting a change you do not fully follow
  2. 2Read the explanation — the goal is your understanding, not the model's

What gets installed

Pick your tool to preview the exact file cosq add writes — byte-for-byte. Prefer copy-paste? Use the copy button on the file.

.claude/commands/explain.md(created)
---
description: Explain the most recent change — what it does, why, and what could break.
---

Walk me through the change we just made:

1. **What** it does, in plain language.
2. **Why** this approach over the alternatives you considered.
3. **What could break** — the edge cases, the assumptions, the blast radius.
4. One thing I should verify myself before trusting it.

Be concise and concrete. Cite the specific files and lines you changed.