Communitygithub.com

研究

調查一個開放性問題,並回傳有依據、附帶來源的調查結果。

研究 是什麼?

此技能「研究」專用於需要釐清未知資訊的場景,其目標是透過系統性調查,將假設替換為確鑿證據,並坦承仍存在的未確定性。工作流程首先要求精確定義問題,接著優先搜尋本地倉庫與文件,再查閱外部 SDK、框架或 API 的官方文件。當答案可能隱藏時,需以多種方式(如按檔案、符號、呼叫者或歷史記錄)進行交叉掃描。最後,將所有發現整合,並清楚標註每個發現的來源。此技能支援狹義查詢、多個獨立問題平行調查,以及未知規模的探索(持續進行直到沒有新發現)。輸出格式包含原始問題、每項發現及其來源、仍未確定或無法驗證的事項,以及建議的下一步行動。它特別強調區分「已驗證」與「推測」的資訊,並如實報告相互矛盾的證據,而非選擇較整齊的敘述。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/research

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

研究 是做什麼的?

當下一步取決於某些尚不明確的資訊時,請使用此技能。研究 回答問題;它不進行實作。

這是典型的研究路徑。deep-dive、sciomc 和 autoresearch 都會匯入此處。

目標

用證據取代假設,並坦率說明仍屬未確定的事項。

工作流程

  1. 精確陳述問題,直到足以判斷何時已得到解答。
  2. 優先搜尋儲存庫及其文件 — 本地證據優於記憶。
  3. 對於外部 SDK、框架或 API,請查閱官方文件。
  4. 當答案可能隱藏時,以多種方式掃描:依檔案、依符號、依呼叫者、依歷史。
  5. 將發現綜合整理,每項發現都應附上其來源。

規模

  • 狹義查詢 — 直接回答。
  • 多個獨立問題 — 平行調查。
  • 未知規模的探索 — 持續進行,直到額外的遍歷沒有發現新內容。

規則

  • 引用來源:檔案與行號,或查閱的文件。
  • 區分已驗證的資訊與推測的資訊。
  • 報告相互矛盾的證據,而非選擇較整齊的敘述。
  • 不要在研究的副作用中進行實作。

輸出

  • 問題
  • 每項發現及其來源
  • 仍屬未知或無法驗證的事項
  • 建議的下一步(如果有的話)

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

agent-doc-discipline

Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 sediment pass; opt-in for any other agent-facing doc edit. The companion of minimal-code-discipline: that one disciplines code, this one disciplines papers.

ai-slop-cleaner

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

ask

Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly

ask-navigator

Shipyard

autopilot

Full autonomous execution from idea to working code

autoresearch

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

cancel

Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state

configure-notifications

Configure notification integrations (Telegram, Discord, Slack) via natural language

debug

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

deepinit

Deep codebase initialization with hierarchical AGENTS.md documentation

deep-interview

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

drydock

Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check to audit drift.

execute

Carry an approved task through to working, verified code

external-context

Invoke parallel document-specialist agents for external web searches and documentation lookup

graph

Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery

harbor

Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence. Agent-autonomous for facts and for actions covered by standing authorization; signed for every new judgment. Never merges.

hud

Configure HUD display options (layout, presets, display elements)

launch

Shipyard

loft

Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks. Use when a design question stalls in words, when a navigator map carries a loft ticket, or when a spec discussion reaches

minimal-code-discipline

YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away

相關技能