테스트 설계, 취약점 진단, 품질 보증 (1.3만건)
Pack an EXTERNAL repository into one AI-friendly file (markdown/xml/json) for third-party analysis, security audits, or handoff. Do NOT use for the current project — it's already read lazily.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unified verification: build → lint → test → type-check → coverage. Use for 'is it green' / 'run all checks'; auto-called by mk:cook. NOT for lint only (mk:lint-and-validate).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validates an approved plan across 8 dimensions before build — incomplete acceptance criteria, missing dependencies, unresolved risks. Use after Gate 1, before Test.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically QA-tests a web app and fixes bugs: test, then iteratively fix, re-verify, commit each fix. Tiers: Quick, Standard, Exhaustive. Produces before/after health scores and fix evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a GitHub PR with a shallow correctness/security/breaking/AI-slop checklist and emits a verdict; optionally posts via gh. NOT for own-diff audit (mk:review); NOT for replying (mk:respond-pr).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Session-persistent browser automation via Playwright CLI: form filling, screenshots, data extraction, multi-step flows. NOT for autonomous flows (mk:agent-browser) or .spec.ts E2E code (mk:qa-manual).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spec-driven manual QA and Playwright E2E generation: navigates apps like a human tester, producing reports or .spec.ts files. Prompts for credentials. NOT for autonomous flows (mk:agent-browser).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maps test coverage to plan acceptance criteria and flags requirements with no tests. Use during Test/Review phases. NOT for running tests (mk:testing); NOT for structural review (mk:review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate visual artifacts: explanations, diagrams, slides, diff views. NOT plan-as-HTML (mk:visual-plan), live media gen (mk:multimodal), or browser QA (mk:qa).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
YC Office Hours-style validation for a new idea before code exists: tests demand (Startup mode) or develops an unvalidated idea (Builder mode). For reviewing an existing plan use mk:plan-ceo-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Vue 3 testing best-practices review: Vitest + Vue Test Utils for components, composables, Pinia, Router, async/Suspense, forms, a11y, plus Playwright E2E strategy. Advisory only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writing tests, running validation, and (TDD mode) red-green-refactor. Active in Test + Build phases. NOT for coverage-gap mapping (mk:nyquist) or sprint contracts (mk:sprint-contract).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Chief Security Officer mode: infrastructure-first audit of secrets, dependency supply chain, CI/CD, LLM/AI security, OWASP Top 10, STRIDE, active verification. Daily/comprehensive, trend tracking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Linting and static analysis after code edits. Triggers on lint, format, check, validate, types. NOT for full build verification (mk:verify) or test coverage (mk:testing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read-only audit of .codex/ structural overhead: 'remove X save Y tokens' vs the context window. NOT for cost tracking (budget skill); NOT for runtime read/compact decisions (mk:context-engineering).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runtime router for context decisions: read-more/stop/ask/assume/delegate, minimal read-set, compaction timing. Model: Write/Select/Compress/Isolate. NOT for .codex/ overhead audit (mk:context-audit).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Workflow navigator: scans project state (plans, reviews, tests, git) and recommends the next pipeline step. Use for 'what next?' or 'where am I?'. NOT for complexity routing (mk:scale-routing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Vue 3 testing best-practices review and recommendations — designing and auditing Vitest + Vue Test Utils tests for components, composables, Pinia stores, Vue Router, async/Suspense, Teleport, forms, and accessibility, plus Playwright E2E test-design strategy. Advisory/review only — recommends patterns and flags test smells; does not run tests. Complements mk:vue-best-practices (feature code). Invoke for "review my Vue tests", "how should I test this component/composable/store", or "Vue test best practices".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browser automation CLI for agents: navigate, click/fill, screenshot, extract data, test apps, Electron/Slack, cloud browsers. NOT for the user's real Chrome profile/cookies (mk:chrome-profile).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Advanced vulnerability analysis principles. OWASP Top 10 baseline + current threat landscape awareness, Supply Chain Security, attack surface mapping, risk prioritization. Use when performing security audits, threat modeling, or OWASP reviews. NOT for STRIDE/CSO-mode infrastructure audits (see mk:cso).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unified verification: build→lint→test→type-check→coverage. Use for 'is everything green', 'run all checks', 'verify build'. Auto-called by mk:cook. NOT for lint/format only (see mk:lint-and-validate); NOT for test-to-requirement coverage mapping (see mk:nyquist).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when analyzing harness trace logs to surface recurring failure patterns and suggest harness improvements. Scatter-gather pattern across last N runs with mandatory HITL gate before any change is applied. Triggers on /mk:trace-analyze, "analyze traces", "find patterns in harness runs", or after a model upgrade flagged dead-weight-audit-needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Angular v20+ patterns: components, signals, services, forms, routing, HTTP, testing, SSR. Auto-activates on .ts files in Angular projects (angular.json detected).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing tests, running validation scripts, or (in TDD mode) enforcing red-green-refactor cycle. Activates during Phase 2 (Test) and Phase 3 (Build). NOT for coverage gap mapping (see mk:nyquist); NOT for sprint contract negotiation (see mk:sprint-contract).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.