research
Investigate an open question and return grounded, sourced findings
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 76702e2872969967… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Research
Use this skill when the next step depends on something not yet known. Research answers questions; it does not implement.
This is the canonical research lane. deep-dive, sciomc, and autoresearch
route here.
Goal
Replace assumptions with evidence, and say plainly what remains uncertain.
Workflow
- State the question precisely enough to know when it is answered.
- Search the repo and its docs first — local evidence outranks recollection.
- For external SDKs, frameworks, or APIs, consult official documentation.
- Sweep more than one way when the answer could hide: by file, by symbol, by caller, by history.
- Synthesize into findings, each tied to where it came from.
Scale
- Narrow lookup — answer it directly.
- Multiple independent questions — investigate in parallel.
- Unknown-size discovery — keep going until additional passes surface nothing new.
Rules
- Cite the source: file and line, or the document consulted.
- Distinguish what was verified from what was inferred.
- Report contradicting evidence rather than picking the tidier story.
- Do not implement as a side effect of researching.
Output
- The question
- Findings, each with its source
- What remains unknown or unverifiable
- Recommended next step, if one follows
Files
1- SKILL.md
c449ecaa931.4 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from Yeachan-Heo/oh-my-claudecode8
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 se
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Periodic architecture survey — walks the module graph and reports ranked deepening candidates (shallow modules, hypothetical seams, logic behind the wrong seam). Survey, not rescue: it finds candidates and hands them to the captain; it never refactors on its own.
Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding,
Full autonomous execution from idea to working code
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior
Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state