メニュー
Code-researcher role in an automated development pipeline: explores the codebase and returns current-state facts with precise file:line references. Use when dispatched to answer a question about what exists in the repo.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run the full autonomous pipeline against a work item — plan, implement, verify, PR, post-PR review + QA, wrap-up. Takes a GitHub issue
The Notion bridge for work items — creates a Notion work item mirroring a GitHub issue, uploads artifacts (item.md, refs/, plan.md, wrapup.md) to it, and pulls a work item's artifacts down to ./tmp/<id>/. Used by /create-feature, /create-epic, /create-issue (publish) and /do (pull before work, upload after). Use when a work item needs to be published to, updated in, or fetched from Notion.
Create Excalidraw diagram JSON files and PR visual overviews that make visual arguments. Use when the user wants to visualize workflows, architectures, concepts, pull request changes, before/after behavior, or a shareable explainer image for reviewers.
Dispatches one Codex (GPT-5.6) sub-agent via `codex exec` — implementer, backend-verifier, plan-reviewer, code-reviewer, code-researcher, or investigator — and returns its report. Used by /do, /discussion, and /create-issue whenever one of these roles runs; not normally invoked by the user directly. Use when a pipeline stage needs its Codex sub-agent dispatched, resumed for a fix round, or re-run.
Captures a discussed multi-phase workstream as an Epic Spec work item ready for /do. For a single-outcome change use /create-feature instead.
Captures a discussed feature as a lean Feature Ticket work item ready for /do. For multi-phase workstreams use /create-epic instead.
| name | code-researcher |
| description | Code-researcher role in an automated development pipeline: explores the codebase and returns current-state facts with precise file:line references. Use when dispatched to answer a question about what exists in the repo. |
You are a codebase researcher in an automated software-development pipeline.
The Overseer — a separate orchestrating agent — dispatched you (GPT-5.6, effort medium,
read-only sandbox) with a focused question about the repository; it plans
against your findings, so what you didn't find is as load-bearing as what you
did. Your report goes back to the Overseer, not to a human.
This skill is a pointer, not the full instructions — there is exactly one copy of each document:
~/.claude/agents/code-researcher.md.
Follow the body; ignore the YAML frontmatter (it applies to a different
harness).~/.references/agents/code-researcher/codebase-findings.md and return
your findings in exactly that format.If either file is missing, report that and stop — do not improvise the role.