「verify」の検索結果

Build error triage: detect language, load fix patterns, auto-retry. Chains into mk:verify. NOT for runtime errors (mk:fix); NOT for architecture debugging (mk:investigate).

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Use when autonomously improving a measurable scalar metric through bounded, git-tracked iterations: modify one scoped change, verify, keep or revert. Triggers on /mk:loop, 'optimize coverage/bundle size/lint count', 'iterate until the metric improves'. NOT for subjective cleanup (see mk:cook), known-root-cause bugs (see mk:fix), behavioral grading (see mk:evaluate), or shipping (see mk:ship).

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Use when transforming existing code into agent-consumable surfaces — CLI (npm-publishable), MCP server (stdio/SSE/Streamable HTTP), and a companion skill. Triggers on 'agentize', 'henshin', 'expose as MCP', 'wrap as CLI', 'publish to npm', 'make LLM-accessible', 'turn into agent tool', 'expose feature as tool'. Runs when the user has existing code and wants to ship it to agents. NOT for building new code from scratch (see mk:bootstrap); NOT for reviewing or verifying existing code (see mk:review).

日本語の概要は準備中です。原文の説明を表示しています。

Build error triage: detect language, load fix patterns, auto-retry. Use for 'build failed', 'fix compilation', 'type error'. Chains into mk:verify. NOT for runtime errors (see mk:fix); NOT for architectural debugging (see mk:investigate).

日本語の概要は準備中です。原文の説明を表示しています。

Generate release-unit development plans from professor-triage completed (verify-done) issues, grouping by priority and size

日本語の概要は準備中です。原文の説明を表示しています。

Multi-angle release quality verification using parallel expert review teams

日本語の概要は準備中です。原文の説明を表示しています。

Research-validated planning — research → plan → verify cycle for high-confidence implementation plans

日本語の概要は準備中です。原文の説明を表示しています。

Stage and verify Fusion exports, drawing PDFs, flat-pattern DXF, viewport images and local renders. Use for engineering deliverables, not automatic publication or release.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare, execute and verify authorized Fusion CAD changes using resolved entities, explicit units and state-bound plans. Use for reviewed parameter, sketch, feature, assembly or configuration operations.

日本語の概要は準備中です。原文の説明を表示しています。

Query the witness-anchored ruLake cache — search, verify, explain, or refresh. Returns ranked results plus a decision_trace block with cost, latency, witness match, and substrates used.

日本語の概要は準備中です。原文の説明を表示しています。

Document-driven workflow for implementing, reviewing, and verifying Chisel processor and memory-subsystem RTL. Use when Codex must work from maintained Architecture and Design, trace a complete integration surface, reason in synthesized-hardware terms, keep source-adjacent _codex.md summaries current, avoid redundant or overprotective logic, or run focused functional verification.

日本語の概要は準備中です。原文の説明を表示しています。

Verify data validity through Openapi Trust - email deliverability, mobile number HLR checks, IP reputation, URL safety scans, document-based identity verification (IDV). Use for anti-fraud validation of user-provided contact data and identities.

日本語の概要は準備中です。原文の説明を表示しています。

Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.

日本語の概要は準備中です。原文の説明を表示しています。

Detects fabricated content, false citations, and unverifiable claims in agent outputs. Uses source verification and consistency checking. Activate on 'detect hallucination', 'fact check', 'verify claims', 'check accuracy', 'find fabrications'. NOT for validation (use dag-output-validator) or confidence scoring (use dag-confidence-scorer).

日本語の概要は準備中です。原文の説明を表示しています。

Validate alignment quality with insert size distribution, proper pairing rates, GC bias, strand balance, and other post-alignment metrics. Use when verifying alignment data quality before variant calling or quantification.

日本語の概要は準備中です。原文の説明を表示しています。

Verify that insulin pump supplies (provided by patient or family) will be available throughout the hospitalization to support continued pump use. Triggered by questions such as "Do we have sufficient pump supplies for the hospital stay?"

日本語の概要は準備中です。原文の説明を表示しています。

Assesses whether a patient performs self-monitoring blood glucose (SMBG) fingerstick calibrations as required for their real-time CGM system. Triggers include: 'Verify patient performs fingerstick calibrations', 'Ensure calibration schedule is followed'.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates basal insulin rates through basal rate testing across different time periods and adjusts as indicated. Triggered by clinician orders to 'Perform basal rate test to verify pump settings' or 'Check basal rates during periodic pump review'.

日本語の概要は準備中です。原文の説明を表示しています。

This skill guides clinicians to assess bolus calculator settings when reviewing pump settings or verifying carb ratio and sensitivity factor during clinic visits. It evaluates insulin-to-carbohydrate ratio, insulin sensitivity factor, glucose targets, and active insulin time for embedded bolus calculators in CSII.

日本語の概要は準備中です。原文の説明を表示しています。

Suggests that clinicians continue CSII in hospitalized patients with type 1 or type 2 diabetes when the institution has clear protocols for evaluating pump candidates and appropriate monitoring and safety procedures. Trigger phrases include: 'Admitted patient on pump, check hospital pump policy' and 'Inpatient with diabetes using pump, verify institutional guidelines'.

日本語の概要は準備中です。原文の説明を表示しています。