「coverage」の検索結果

Use this skill whenever the user asks to inspect, audit, review, assess, or evaluate a codebase/project for maintainability, extensibility, architecture, reliability, security, testing, engineering quality, or AI-agent/prompt/tooling risks. Also use this when invoked by `/inspect`. It performs a read-only, evidence-backed, multi-agent project inspection with complete file coverage, per-dimension scoring, blunt technical findings, and explicit degraded-mode disclosure.

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

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

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

Validate sequencing and cross-layer readiness before phase slicing, including coverage and consistency hard gates

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

Systematic methodology for verifying that IA, BE, and FE specification layers are mutually consistent. Covers coverage matrices, field mapping checks, error code propagation, access control consistency, and data contract drift detection.

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

Use when working with Confluence Deep — deep Confluence management covering spaces, pages, content analytics, permissions, and workspace health. Use when performing deep audits of Confluence usage, analyzing content freshness, reviewing space permissions, or assessing documentation coverage across an Atlassian Confluence instance.

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

Use when working with Deepsource — deepSource code analysis management. Covers automated code reviews, issue detection, antipattern analysis, coverage tracking, and analyzer configuration. Use when managing DeepSource projects, reviewing detected issues, configuring analyzers, or tracking code health metrics.

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

Use when working with Codeowners — cODEOWNERS file management covering ownership mapping analysis, coverage gap detection, team assignment validation, orphaned path identification, and review requirement auditing. Use when auditing code ownership across repositories, identifying unowned code paths, validating team configurations, or optimizing pull request review workflows.

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

Use when working with Cucumber — cucumber BDD testing management and analysis. Covers feature file organization, step definition mapping, scenario tagging, Gherkin syntax validation, test report parsing, and step reuse analysis. Use when managing Cucumber test suites, investigating BDD scenario failures, or reviewing feature file coverage.

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

Use when working with Codacy — codacy code quality management. Covers automated code reviews, pattern configuration, coverage tracking, security analysis, and repository settings. Use when managing Codacy projects, reviewing code patterns, configuring quality gates, or tracking code quality trends.

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

Use when working with Aws Backup — aWS Backup vault, plan, and job management. Covers backup vaults, backup plans, backup selections, recovery points, backup jobs, restore jobs, and compliance frameworks. Use when auditing backup coverage, checking backup job status, reviewing recovery points, or validating backup compliance.

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

Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory, coverage-bounded integrity checks, two-stage peer review, and auditable quality-assurance artifacts. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow, 연구부터 논문까지, 연구 주제 설정부터 논문 완성까지, 논문 전체 워크플로.

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

Evaluate recommender system quality for the CSX4207 Vinyl Record Store. Use whenever you must compute or report recommender metrics (Precision@k, Recall@k, HitRate@k, MRR, MAP@k, NDCG@k, coverage, diversity, novelty, serendipity, personalization), design an evaluation protocol/split, run a baseline comparison, or write the evaluation section of a course deliverable. Covers formulas, JavaScript reference implementations, and the reporting checklist.

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

Maintain skills wiki health - check links, naming, cross-references, and coverage

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

Consistent radii, pixel-perfect alignment, state coverage, and the details that signal design quality. Use when polishing designs, auditing quality, or evaluating whether a design is ready to ship.

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

Micro-decision analysis. Catalog the border radii, spacing scales, type sizes, and state coverage that most people miss. Use when auditing design systems, evaluating craft quality, or training granular perception.

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

Run or maintain the full tdmcp repo quality-audit team: command sweeps, all package/Makefile/CI gates, security review, usability/flow review, refactor/test-gap analysis, coverage hardening, QA, and follow-up fix waves. Use whenever the user asks for a complete audit, improve repo/code quality, test all commands, find security/usability failures, refactor debt, add missing tests, re-run the audit, continue a previous quality wave, or verify the repo is ready.

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

Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff review, regression review, security review, or wants high-signal issues plus a prioritized fix path without editing files.

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

Produces thorough, multi-source cited research reports from web and news without paid APIs. Use when the user asks for deep research, landscape analysis, competitive intel, market research, or a cited report needing broad source coverage.

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

Helps detection engineers identify coverage blind spots in system command execution detection rules, evaluate bypass risks, and reduce false negatives. Strictly limited to system command execution rules; not applicable to browser credential theft or abnormal process creation without command semantics.

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

Use when: analysing a project's test health — coverage, robustness, and CI integration.

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

Use when: UI standards discovery, UI pattern research, UI audit, pre-handoff UI state coverage review, or when a business-specific child skill needs a stack-agnostic UI methodology to load first.

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

Reproduce ai-repo PR checks locally with Poe and CI scripts, including per-package typecheck and coverage behavior. Use when validating changes before push or when user asks which local commands match CI.

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

Build, maintain, and run conformance tests for canonical App-in-Skill projects created by kelly-app-skill-creator. Use when a Kelly app skill needs contract checks, local server smoke tests, responsive browser acceptance, temporary open-source Busabase integration, environment-gated Busabase Cloud OAuth verification, lazy provisioning checks, persistence tests, AirApp parity tests, or CI coverage. Keep app creation in kelly-app-skill-creator and own only the reusable test harness, per-skill fixtures, execution gates, diagnostics, and truthful pass/fail/skip reporting.

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

Generates the monthly revenue-accountable marketing report that B2B SaaS marketing leaders deliver to CEOs, CFOs, executive teams, and boards. Use when preparing the monthly CEO report, drafting the marketing section of a board deck, defending budget decisions, diagnosing pipeline gaps, or transitioning marketing from MQL/SQO reporting to revenue, CAC payback, and forward pipeline coverage. Designed for B2B SaaS demand generation leaders who own pipeline targets across segments, geos, and motions, and need to explain marketing's revenue contribution in executive language.

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