「testing」の検索結果

Holoscan Sensor Bridgeのテスト文書から機器構成に合う自動実行項目を選び、実機での合否判定と結果レポート作成まで進めるスキル。

• HSBのテスト計画を実機で確認したいとき
• 接続センサーに合う自動テストの選定
• 失敗したテストのログ調査

Dynamoの分離型・複数ノード構成で、GPU間の高速通信に必要な設定と機能を読み取り専用で点検し、転送テストの準備状況や次の確認手順を示すスキル。

• デプロイ後の通信準備状況の確認
• 性能測定前の転送設定の点検
• 通信が原因と思われる遅延の調査

Holoscan SDK 5.xのタグやコミットを指定してソースからビルドし、既存の変更を保ちながら、環境確認、構成の選択、サンプルテストによる動作検証まで進めるスキル。

• 未公開のEarly Access機能を試したいとき
• 修正済みSDKをビルド・検証したいとき
• デバッグ構成やC++専用構成の作成

BlueFieldやConnectXでAES-GCMの暗号化・復号を実装する作業を支援します。対応鍵長やバッファ権限の確認、テスト、認証タグ検証失敗の扱いを案内します。

• デバイスのAES-GCM対応鍵長の確認
• 暗号化・復号バッファの権限設定
• 公開テストデータで暗号処理を検証したいとき

医療用語の音声認識評価を始める前に、APIキーとPython環境を確認し、合成した例文の読み上げと文字起こしでNVIDIAの音声サービスへの接続を検証します。

• 医療用語の音声認識評価の準備
• 新しい環境からのAPI接続確認
• 読み上げと文字起こしの一連テスト

工場の作業映像から手順の抜けや順序違いを検出するサービスの構築・運用を支援します。DeepStreamによる映像処理とVLMによる動作分類の評価、遅延測定も扱います。

• 組立作業の手順確認サービスを作りたいとき
• 動画や産業用カメラで動作検証したいとき
• 動作分類や手順判定の不具合を調べたいとき

KERMTの初期環境を整え、DockerとGPU接続の確認、必要なコンテナイメージの構築、内部でGPUを認識できるかの動作確認まで行うスキル。

• 新しいマシンでKERMTを使いたいとき
• コンテナ内のGPU接続確認
• KERMTイメージの初回構築

Create or update GoClaw agent skills with eval-driven iteration. Use for new skills, skill scripts, references, benchmark optimization, description optimization, eval testing, extending agent capabilities.

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

Golang library and framework selection — vetted production-ready options by category (web, database, testing, logging, messaging), new and experimental stdlib packages, standard-library-first tradeoffs, and maturity signals (maintenance, license, importer counts). Apply when the user asks for library suggestions, wants to compare alternatives, needs to choose a library for a specific task, or when a new dependency is being added to the project. Not for a specific library's API once chosen (→ See that library's dedicated skill, e.g. `samber/cc-skills-golang@golang-samber-lo`), nor for go.mod mechanics, upgrades, or vulnerability audits (→ See `samber/cc-skills-golang@golang-dependency-management` skill).

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

Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.

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

Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification, suite lifecycle, and advanced patterns like Eventually, JSONEq, and custom matchers. Apply when the codebase imports github.com/stretchr/testify.

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

Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil panics or slice aliasing (→ See `samber/cc-skills-golang@golang-safety` skill), dependency vulnerability scanning with govulncheck (→ See `samber/cc-skills-golang@golang-dependency-management` skill), or wiring security scanners into CI pipelines (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).

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

Golang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber/cc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber/lo vs mo vs ro, DI cluster, safety vs security), and configures the project's agent-config file (CLAUDE.md, AGENTS.md, GEMINI.md, Cursor rules, or Copilot instructions) to force-trigger skills in a project (/golang-how-to configure).

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

Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration layering, version embedding, exit codes, I/O patterns, signal handling, shell completion, argument validation, and CLI unit testing. Also triggers when code uses cobra, viper, or urfave/cli. For cobra-specific APIs → See `samber/cc-skills-golang@golang-spf13-cobra` skill; for viper configuration layering → See `samber/cc-skills-golang@golang-spf13-viper` skill.

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

Golang CLI command tree library using spf13/cobra — cobra.Command, RunE vs Run, PersistentPreRunE hook chain, Args validators (NoArgs, ExactArgs, MatchAll, custom), persistent vs local flags, command groups, ValidArgsFunction, RegisterFlagCompletionFunc, ShellCompDirective, usage/help template customization, man-page and markdown doc generation, and testing with SetArgs/SetOut/SetErr. Apply when using or adopting spf13/cobra, or when the codebase imports `github.com/spf13/cobra`. For configuration layering alongside cobra, see the `samber/cc-skills-golang@golang-spf13-viper` skill. For general CLI architecture (project layout, exit codes, signal handling, I/O patterns), see `samber/cc-skills-golang@golang-cli`.

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

Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.

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

[omh] Hostile scenario testing: adversarial QA and fix loops. Use when the user says: ultraqa, adversarial qa, hostile scenarios, e2e qa, real-world qa, qa scenario, release qa, 敵対的QA.

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

Run real E2E tests against Claude CLI in pytest and tmux modes

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

Run PR-grade real Codex E2E validation through claude-tap, including resume turns, multiple tool calls, optional image input, viewer verification, and screenshot evidence.

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

Test JS logic embedded in HTML using two-layer strategy - Python unit tests + Playwright browser integration tests

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

Use when verifying OpenClaw gateway fixes end-to-end, testing skill loading after restart, or running integration tests against the local Nexu+OpenClaw stack. Triggers on "e2e test", "verify fix", "test gateway", "test skills loading".

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

Complete browser automation with Playwright. Auto-detects dev servers, writes reusable test scripts, and supports screenshots, responsive checks, UX validation, login flows, link checks, and arbitrary browser automation. Use when the user wants to test a website, automate browser interactions, validate web functionality, or perform browser-based testing.

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

Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.

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

SUPERSEDED by /claudex-loop (formerly /crucible; its docs-aware mode covers this variant) — prefer that skill unless you explicitly want this one. Two-act plan hardening with living documentation. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan, one question at a time, challenging it against your project's existing domain model and glossary (CONTEXT.md), sharpening fuzzy terms, stress-testing with concrete scenarios, cross-referencing code, and updating CONTEXT.md + ADRs inline as decisions crystallise. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-with-docs-codex", "grill me against the docs then have codex review", "stress-test this against our domain model then get a second model on it", or is about to build something high-stakes in a project with established terminology/ADRs and wants alignment, documentation, AND a cross-model sanity check. Builds on Matt Pocock's grill-with-docs (MIT). NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.

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