测试与安全技能

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).

中文简介正在准备中。当前显示原文说明。

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).

中文简介正在准备中。当前显示原文说明。

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).

中文简介正在准备中。当前显示原文说明。

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).

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

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).

中文简介正在准备中。当前显示原文说明。

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 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).

中文简介正在准备中。当前显示原文说明。

Validates an approved plan against 8 dimensions before Phase 3 begins. Catches incomplete acceptance criteria, missing dependencies, and unresolved risks. Use after Gate 1 approval and before Phase 2 (Test). Produces a validation report with pass/fail per dimension.

中文简介正在准备中。当前显示原文说明。

Angular v20+ patterns: components, signals, services, forms, routing, HTTP, testing, SSR. Auto-activates on .ts files in Angular projects (angular.json detected).

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

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).

中文简介正在准备中。当前显示原文说明。

Use when generating visual artifacts — explanations, diagrams, slides, or diff visualizations. Triggers on "explain X visually", "diagram this", "show as slides", "diff against main". NOT for rendering a plan as HTML (see mk:visual-plan), live media generation (see mk:multimodal), browser QA (see mk:qa), or plan critique (see mk:plan-ceo-review).

中文简介正在准备中。当前显示原文说明。

Reviews a GitHub PR with a single shallow correctness/security/breaking/AI-slop checklist and emits a verdict; optionally posts it via gh pr review. Use to review an external or teammate PR. NOT for deep pre-landing audit of your own diff (see mk:review); NOT for responding to received review comments (see mk:respond-pr).

中文简介正在准备中。当前显示原文说明。

Automatic quality control, linting, and static analysis after code modifications. Triggers on: lint, format, check, validate, types, static analysis. NOT for full build verification (see mk:verify); NOT for test coverage (see mk:testing).

中文简介正在准备中。当前显示原文说明。

Resolve an in-progress git merge or rebase conflict end to end: read the conflict state, recover each side's original intent, resolve every hunk, run the project's checks, and prepare the merge/rebase for an explicitly approved finish. Use when asked to "resolve merge conflicts", "fix this rebase", "finish the merge", or when `git status` shows conflicted (unmerged) paths. NOT for the full ship pipeline that merges the base branch first (see mk:ship); NOT for debugging a runtime bug or test failure unrelated to a conflict (see mk:investigate / mk:fix).

中文简介正在准备中。当前显示原文说明。

YC Office Hours — product validation for a new product, feature, or side-project concept. Startup mode tests demand; Builder mode develops an unvalidated product idea. Use when the user asks whether something is worth building or has an idea whose problem/value is not yet validated. Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use BEFORE a plan exists. For reviewing an existing plan, use /mk:plan-ceo-review.

中文简介正在准备中。当前显示原文说明。

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.

中文简介正在准备中。当前显示原文说明。

Test-to-requirement coverage mapping. Reads plan acceptance criteria and test files, produces a coverage gap report showing which requirements have no tests. Use during Phase 2 (Test) or Phase 4 (Review) to verify test completeness. Named after the Nyquist sampling theorem — sufficient test coverage prevents aliased (missed) requirements. NOT for running tests (see mk:testing); NOT for structural code review (see mk:review).

中文简介正在准备中。当前显示原文说明。