Video & Animation

|

Use for authorized digital forensics including memory dumps, disk timelines, PCAP investigation, artifact triage, and IR evidence preservation.

Self-referential loop until task completion with configurable verification reviewer

Evaluate finished work for defects, risk, and simplification before it ships

Investigate an open question and return grounded, sourced findings

Install or refresh oh-my-claudecode for plugin, npm, and local-dev setups from the canonical setup flow

Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release

Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs

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

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.

Shipyard

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

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

Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions

Carry an approved task through to working, verified code

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

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

Deep codebase initialization with hierarchical AGENTS.md documentation

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.

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

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

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

Diagnose and fix oh-my-claudecode installation issues

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