e
Explain a file, error, design, diff, or concept like a helpful engineering colleague: grounded in evidence, concise, and with useful follow-up threads. Use when the user asks for a clear explanation o
SKILL.mdskills/e/SKILL.md
GitHubExplain
Use this as the Codex and Pi equivalent of /up:e.
- If the user named a file, error, diff, or behavior, inspect it before explaining. If they did not, infer the most recent clear topic and state what you selected; ask once only if no target is clear.
- Lead with the mechanism that answers the question. Assume the reader only vaguely remembers surrounding context.
- Give evidence in plain language, normally one to four paragraphs. Avoid doc dumps, invented terminology, and unexplained shorthand.
- End with up to three deeper follow-up threads only when they would add real value.