Manage Git worktrees as OMK safe isolated coding lanes for complex, risky, or parallel work.
Clone important project dependency source code into an ignored local workspace so KiloCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos locally readable. Do not use for ordinary API/docs questions where @librarian is enough.
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping
Chief-only workflow for heavy coding sessions, multi-phase implementation, and risky refactors. Use for complex work that needs planning, review gates, and persistent progress tracking.
Loop engineering runtime Grill + Monitor
Configure and improve oh-my-kilocode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
Test an oh-my-kilocode-slim release candidate or bugfix before publishing. Use when validating a packed plugin artifact, release branch, crash fix, KiloCode runtime compatibility, or model-specific smoke test such as KiloCode 1.17.11 message transform regressions.