1.6천건 · 관련도순
Generates comprehensive, context-aware code review checklists tailored to the specific codebase, programming language, and team standards. Analyzes PR diffs and suggests what reviewers should focus on.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agent system design patterns distilled from the OpenClaw codebase. Gateway-centric control, Session Key hierarchy, Binding routing, Lane Queue concurrency, Sub-agent Spawn+Announce, 4-tier automation, Plugin architecture, Policy Chain, Failover strategies. Triggered by "gateway", "session", "binding", "lane", "spawn", "announce", "heartbeat", "cron", "hook", "plugin", "policy", "failover" keywords.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structures git branches and worktrees: keeps unrelated changes on separate branches, isolates each in its own worktree created so the repository's setup runs, records dependencies with git-machete, and recombines them into a temporary mixdown branch for local testing. Use before creating any branch or worktree in a codebase that works on more than one branch, including branching off the default branch to start a change; when starting work in a fork, clone, or third-party checkout; when choosing what a new branch should be based on; when a branch is growing a second unrelated concern; when deciding whether to stack branches or keep them independent; when preparing a change for a pull request or patch submission; when handed an existing worktree or branch to implement and commit in a fork; or when a local build needs several in-progress branches combined. Not needed where the repository clearly commits everything to the trunk, or holds notes or personal data rather than code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triages reviewer comments on a GitHub PR: verifies each against the codebase, then accepts/pushes back/clarifies, replies in-thread. NOT for reviewing (mk:review-pr); NOT for fixes (mk:fix).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes ticket complexity and dependencies against the codebase before sprint planning. NOT for writing plans (mk:plan-creator); NOT for scope review (mk:plan-ceo-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fast parallel codebase scouting — searches many directories at once, returning a file map + architecture fingerprint. Use before planning or cross-dir work. NOT for deep single-file reads.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep multi-source technical research with citations — tech evaluation, ecosystem/standards comparison. NOT for API docs (mk:docs-finder), codebase discovery (mk:scout), or project Q&A (mk:ask-me).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate initial docs/ from codebase analysis when a project has none. Triggers on 'init docs', 'create/generate documentation'. NOT for updating existing docs (mk:document-release).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Surfaces architectural friction and proposes deepening refactors (shallow to deep modules). Renders via mk:preview. NOT for debate (mk:party); NOT for plan critique (mk:plan-ceo-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Answer factual project questions (codebase, architecture) with cited evidence. NOT for brainstorming, trade-offs (mk:party), debugging (mk:investigate), review (mk:review), or plans (mk:plan-creator).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage reviewer comments on a GitHub PR with receiving-code-review discipline — verify each against the codebase, then accept/push-back/clarify, and optionally reply in-thread. Use when responding to received PR feedback. NOT for giving a review (see mk:review-pr); NOT for implementing the fixes (hand off to mk:fix).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when refining a draft user prompt before sending it to a coding agent. Decomposes goal/context/constraints/acceptance/output-format, detects ambiguity and model-coupled framing, then emits a model-agnostic rewrite. Supports --analyze, --score, and --deep. NOT for prompts from scratch (mk:brainstorming), plans/reviews (mk:elicit), implementation plans (mk:plan-creator), or general codebase scouting (mk:scout).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes ticket complexity and maps dependencies against an existing codebase before sprint planning. Triggers on 'how complex is this ticket', 'what should we work on first', 'can we fit this in the sprint', 'tech review before planning', 'plan the sprint'. NOT for writing implementation plans (see mk:plan-creator); NOT for scope/ambition review (see mk:plan-ceo-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pack an EXTERNAL repository into a single AI-friendly file (markdown/xml/json). Use for third-party library analysis, security audits, or handoff to external LLMs. Do NOT use to pack the current project for inbound context — the host runtime already reads files lazily. Triggers: 'pack this repo', 'snapshot of X', 'export codebase', 'repomix'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a decision needs deep multi-source technical research with cited evidence — technology evaluation, ecosystem comparison, standards/spec fact-finding, "how do others solve X". Triggers on "research X", "deep dive on X", "evaluate X vs Y", "find best practices for X". NOT for library/API doc lookup (see mk:docs-finder); NOT for one-shot URL fetch (see mk:web-to-markdown); NOT for internal codebase discovery (see mk:scout); NOT for project-only Q&A (see mk:ask-me); NOT for comparing solution designs (see mk:brainstorming); NOT for root-cause debugging (see mk:investigate); NOT for wiki ingestion of sources (see mk:wiki-research).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates structured multi-file implementation plans before build. Scope-aware: trivial tasks exit early, simple tasks get fast plans, complex tasks get full research + phase files + validation. Enforces Gate 1. Activated by /mk:plan or /mk:cook. NOT for ticket complexity analysis against an existing codebase (see mk:planning-engine); NOT for CEO-level scope review of existing plans (see mk:plan-ceo-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the project wiki as RAG knowledge source — search wiki pages to answer codebase questions before exploring raw files
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate and maintain a persistent codebase wiki — LLM-built interlinked markdown knowledge base (Karpathy LLM Wiki pattern)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze GitHub issues against current codebase and perform automated triage with priority assessment
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a natural language idea against the project codebase and return structured issue specs
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan the repository for hardcoded secrets, exposed API keys, insecure network configurations, and vulnerable dependencies. Use when the user asks for a security audit, secret detection, credential scan, vulnerability check, or wants to find leaked tokens in the codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit an existing UI for usability, hierarchy, accessibility, and conversion problems. Reviews a live URL, screenshot, or codebase against heuristics and reports prioritized issues with fixes. Use when the user says "audit this UI", "what's wrong with this screen", "UX review", "find the problems", "why is this confusing", or has existing interface to critique. Part of the Product Design set. Can drive a browser for live audits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when user says "simmer this", "refine this", "hone this", "iterate on this", or asks to improve a specific artifact over multiple rounds. Runs an iterative refinement loop with investigation-first judges that read the code, understand the problem, and propose evidence-based improvements. Auto-selects single judge or multi-judge board based on complexity. Works on any artifact type: documents, prompts, specs, emails, creative writing, API designs, pipelines, codebases. Supports multi-file workspace targets, runnable evaluators, and open-ended optimization (model selection, pipeline topology, prompt tuning).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Semantic search, grep, and Q&A across codebases and documentation indexed in CodeAlive. Use when the user mentions "CodeAlive", asks to list or get data sources, list indexed repositories, search code or docs across remote repos, fetch artifact content, or trace call graphs across repositories.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.