Communitygithub.com

调研

针对一个开放性问题进行调查,并返回有据可查的结论。

调研 是什么?

该技能专为需要事实核查或信息收集的场景设计。当下一步决策依赖于未知信息时,使用“调研”技能来获取有据可查的答案,而不是直接实现代码或功能。它遵循一个结构化的流程:首先精确定义问题,然后优先从本地仓库和文档中查找证据,其次是官方 SDK、框架或 API 的文档。该技能支持多种搜索策略,包括按文件、符号、调用者和历史记录进行搜索,以确保全面覆盖。最终输出包括具体的问题、带来源的发现、仍不确定的部分以及推荐的下一个步骤。该技能适用于 Claude Code、Codex 和 Cursor 等 AI 代理平台,帮助开发者避免基于假设做出决策,而是依赖可靠的证据。

兼容平台~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

相关技能