Menu
Explain code, behavior, architecture, or diffs with concrete references to the relevant files.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Release a new version of the project.
Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.
Ask focused clarifying questions to resolve ambiguous requirements before planning or implementing work.
Diagnose failing tests, determine whether code or tests are wrong, and make the smallest passing fix.
Refactor existing code while preserving behavior, keeping changes scoped, and verifying with relevant tests.
Review current code changes for bugs, regressions, test gaps, and project-guideline violations.
| name | explain |
| description | Explain code, behavior, architecture, or diffs with concrete references to the relevant files. |
Topic to explain (optional): $ARGUMENTS
Locate the subject. Identify the files, functions, commands, tests, or diff hunks relevant to the user's question.
Read enough context. Inspect surrounding code, call sites, tests, and configuration needed to explain behavior accurately.
Explain from evidence.
Keep scope tight. Do not refactor, edit files, or run broad commands unless the user asks for implementation work.
Use concise prose with file references when useful. For complex behavior, include the execution path or data flow in the order it happens.
