メニュー
Research a technical topic thoroughly by exploring the codebase and summarizing findings. Use when asked to investigate how something works, research an area of the codebase, trace a data flow, or understand a component in depth.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
| title | deep-research |
| name | deep-research |
| description | Research a technical topic thoroughly by exploring the codebase and summarizing findings. Use when asked to investigate how something works, research an area of the codebase, trace a data flow, or understand a component in depth. |
| context | fork |
| agent | Explore |
| argument-hint | ["topic or question"] |
Research the following topic thoroughly: $ARGUMENTS
Identify the scope of the research. Parse the topic into concrete searchable terms: class names, function names, file name patterns, configuration keys, or framework-specific terms.
Search broadly before reading deeply:
*auth*, *middleware*, *.config.*)Read the most relevant files completely. Do not skim. Missing a detail in a critical file leads to incorrect conclusions.
For key files, check recent git history to understand why things are the way they are:
git log --oneline --follow -20 <filepath>
Read the most informative commit messages. If a commit message references a PR or issue number, note it.
Follow import and dependency chains one level deep. If the main file imports from three other modules, read those modules too.
Synthesize findings into a structured report with these sections:
Overview What this system or component does, in two to four sentences. Write for someone who has never touched this codebase.
Key files A table: file path | one-line description of its role. Include every file you read that was materially relevant.
How it works The main flow, data structures, and key design decisions. Use concrete terms: function names, type names, config keys. Reference file paths and approximate line numbers for the most important details.
Recent changes What changed in the last 20 commits in the relevant area, and why (based on commit messages and diff context).
Open questions Anything that is unclear from the code alone and would benefit from asking a team member or reading documentation. Be specific.
Be precise. If you are uncertain, say so. Do not infer things that are not in the code.