2,982 件 ・ 関連度順
概要と使いどころ
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).
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
Controls error rates across thousands of simultaneous tests in genomics discovery using false-discovery-rate methods (Benjamini-Hochberg 1995; Benjamini-Yekutieli 2001 for arbitrary dependence; Storey q-value with pi0 estimation; local FDR; independent filtering Bourgon 2010; covariate-weighted FDR via IHW Ignatiadis 2016), plus family-wise error control (Bonferroni, Holm) and the GWAS genome-wide threshold. Covers the FDR-versus-FWER choice as the discovery-versus-confirmatory distinction, the dependence assumptions behind BH (PRDS) versus BY, pi0 estimation, the independent-filtering and false-coverage-rate traps, and reproducibility ranking via IDR (Li 2011). Use when correcting p-values from genome-wide tests, choosing between BH/BY/q-value/Bonferroni, setting an FDR threshold, applying IHW or independent filtering, or interpreting q-values. For confirmatory trials with few pre-specified endpoints (closed testing, graphical/gatekeeping), see clinical-biostatistics/multiplicity-graphical.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes species-environment relationships with constrained ordination (CCA, RDA, db-RDA), variance partitioning, indicator species (indicspecies IndVal.g group-equalized), PERMANOVA paired MANDATORILY with PERMDISP (Anderson & Walsh 2013; dispersion confounds centroid tests), Joint Species Distribution Models (HMSC, sjSDM, gjam) with explicit rejection of "residual covariance equals biotic interaction", phylogenetic community ecology (SES_MPD/MNTD), trait-environment via RLQ + fourth-corner with corrected modeltype=6 (Dray 2014), bipartite network metrics (NODF, modularity) with curveball null (Strona 2014), and Mantel-test replacements (dbRDA, GDM) for spatial data. Use when testing how environmental gradients structure communities, identifying habitat indicator taxa, partitioning variance among predictors, deciding whether PERMANOVA significance is location vs dispersion, picking among HMSC/sjSDM/gjam, or replacing Mantel tests for landscape data.
日本語の概要は準備中です。原文の説明を表示しています。
Tests associations between categorical variables in clinical data using chi-square, Fisher's exact, Boschloo, Cochran-Mantel-Haenszel, and modern McNemar variants with calibrated confidence intervals (Wilson, Newcombe, Miettinen-Nurminen). Use when analyzing categorical outcomes, paired binary endpoints, or testing treatment-outcome independence in confirmatory or exploratory clinical trials.
日本語の概要は準備中です。原文の説明を表示しています。
Testing patterns for PHPUnit and Playwright E2E tests. Use when writing tests, debugging test failures, setting up test coverage, or implementing test patterns for ActivityPub features.
日本語の概要は準備中です。原文の説明を表示しています。
Work up a patient with confirmed hypercalcemia using the PTH-dependent vs. PTH-independent algorithm — order the right second-tier tests (PTHrP, 25(OH)D, 1,25(OH)2D, SPEP/UPEP, urinary calcium/creatinine clearance ratio, TSH) to reach a diagnosis. Trigger when a clinician asks "what's causing this hypercalcemia", "how to work up high calcium", "what tests to order for hypercalcemia", "PTH is normal what next", "differential diagnosis of hypercalcemia", or shares a confirmed hypercalcemia and asks for the workup.
日本語の概要は準備中です。原文の説明を表示しています。
This skill suggests follow-up tests for specific comorbidities associated with Cushing's syndrome in patients with adrenal adenoma when CT density is less than 10 Hounsfield units. Use when managing a post-adrenalectomy Cushing's syndrome patient with confirmed adrenal adenoma pathology and low-density imaging (<10 HU).
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends using biochemical tests to screen for hypercortisolism to detect recurrence in patients with ACTH-dependent Cushing's syndrome after surgical remission. It is triggered during postoperative follow-up when the HPA axis has recovered, annually, or sooner if clinical signs of hypercortisolism (e.g., weight gain, hypertension, glucose intolerance) or abnormal late-night salivary cortisol/UFC appear.
日本語の概要は準備中です。原文の説明を表示しています。
Look up NHS England genomic tests for rare and inherited diseases. Use this skill whenever a clinician asks what genetic test to order for a condition, which genes are covered for a specific diagnosis, what commissioning category a genomic test falls under (Core, Specialised, or Highly Specialised), or which tests belong to a specialty group (Neurology, Cardiology, Endocrinology, etc.). Also trigger for questions like what panel is used for a condition, whether there is an NHS test for something, what the R number is for a condition, or whether anything has changed in the genomic test directory. Source: NHS England National Genomic Test Directory for Rare and Inherited Disease v9.0 (April 2026).
日本語の概要は準備中です。原文の説明を表示しています。
Write executable failing tests from a recipe handed to you by the main context. Used by `/tdd` Step 2 and ad-hoc when a phase needs tests-first to drive implementation. Decisions about which scenarios to cover, which categories matter, and which fixtures to use are made by the caller — this skill executes that recipe with code-structure discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for the Tests area of paddock. 44 symbols across 6 files.
日本語の概要は準備中です。原文の説明を表示しています。
How to run tests using remote executor.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic testing methodology for exhaustive branch coverage, edge case identification, and production bug prevention. Use when PR review reveals incomplete test coverage, when tests pass but users report bugs, when code changes break existing features, when verifying all branches and edge cases before merge, when analyzing "it works on my machine" issues, when planning test strategy for new features, or when debugging flaky tests and race conditions.
日本語の概要は準備中です。原文の説明を表示しています。
Use to iterate a change until tests/quality checks pass — bounded run→revise→re-run gated by a numeric threshold, then a judge confirms. Triggers 'iterate to green', 'keep fixing until tests pass'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a diff may lack tests — missing assertions, uncovered branches, over-mocking, no regression test for a bug fix — dispatched by /review-changes, /do-and-judge, /judge, even without 'tests'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing API endpoint tests — integration tests, contract validation, response assertions, mocked external services — even when the user says 'test this route' without naming API testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding, running, or debugging proctmux end-to-end integration tests, especially PTY/TUI behavior, terminal snapshots, unified/client modes, timing flakes, VT100 emulator limits, or files under tests/e2e and internal/testharness/e2e.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use to author, audit, amend, or test-spec a business Feature Spec. The single spec skill — modes draft|init|update|audit|amend create/maintain the tech-free 8-section Feature Spec; draft authors a provisional spec from an idea/requirement (no code yet, Evidence: TBD); tests generates Section 8 TC-{FEATURE}-{NNN} test specifications; sync reconciles §8 TCs ↔ executing test code. Per-mode procedure lives in references/{author,tests,sync}.md.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use when (re)generating the DERIVED technical spec view over code + tests, or reporting canonical §8 TC/test-code drift. A GENERATOR — it projects code + tests into a regenerable per-component view and NEVER authors business content. Modes generate|audit|sync. Per-mode procedure lives in references/{author,sync}.md.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use when scanning the codebase to (re)generate ONE project-reference doc. Parameterized by `--target=<key>`: project-structure | backend-patterns | frontend-patterns | scss-styling | design-system | code-review-rules | domain-entities | feature-spec | docs-index | e2e-tests | integration-tests | seed-test-data | ui-system. Shared 4-phase scan engine; per-target detail lives in references/targets.md. `ui-system` is an orchestrator meta-target (`kind: orchestrator`) that runs the 3 UI child scans in parallel instead of the 4-phase engine.
日本語の概要は準備中です。原文の説明を表示しています。
Build and run EMULATORS locally on Windows with the repository-compatible Visual Studio configuration and SDL runtime architecture. Use whenever Codex compiles, links, tests, launches, or smoke-tests an EMULATORS executable on Windows.
日本語の概要は準備中です。原文の説明を表示しています。