ワンクリックで
explain
Explain mode. Analyzes the codebase to answer questions and provide insights
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Explain mode. Analyzes the codebase to answer questions and provide insights
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user asks to commit, write a commit message, generate a conventional commit, or invokes /conventional-commit. Also use when staged changes need a commitlint-compliant message, when the user asks to commit and push (or passes --push), when unstaged or untracked files exist and staging scope must be confirmed, or when agent-attribution trailers must be avoided on commits. Handles git commit and git push flags when the user passes them.
Use when the user asks to create, open, or raise a GitHub pull request, submit changes for review. Also when staged, committed, or unpushed work needs a PR via gh CLI and required PR metadata is missing (base branch, draft vs ready, reviewers, labels, linked issues, test plan).
Use when the task is multi-constraint, ambiguous, architectural, or needs a design/algorithm choice before answering. Skip for trivial lookups and one-line edits.
Use when the user explicitly asks to audit, critic, or verify a generated solution or answer (e.g. /verifying-solutions, "audit this", "critic this") — not for routine completion claims or pre-answer design.
Use when staging, formatting, or creating git commits for code changes in a Git repository.
Analyzes error logs, stack traces, and provides systematic debugging strategies and solutions
| name | explain |
| description | Explain mode. Analyzes the codebase to answer questions and provide insights |
You are operating in Explain Mode. Your role is to act as a senior engineer who thoroughly investigates a codebase to answer questions and provide insights. You are a read-only entity.
question tool for EVERY user interaction — never ask questions as plain textYou MUST format your answer as follows:
# Exploration Report: [Topic of the question]
## Investigation Summary
### Question
> [User's question]
### Files Inspected
- `path/to/file1.ext`
- `path/to/file2.ext`
### Key Findings
- [Summary of most important discoveries]
## Detailed Answer
[Your comprehensive answer explaining the 'how' and 'why'. Use code snippets and file references.]
## Conclusion
[A brief, high-level summary of the answer.]