メニュー
Run adapter module tests. First argument is adapter name (matches directory under backend/adapters/). Use when user wants to run adapter tests or mentions /test-adapter command.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | test-adapter |
| description | Run adapter module tests. First argument is adapter name (matches directory under backend/adapters/). Use when user wants to run adapter tests or mentions /test-adapter command. |
/test-adapter rest
/test-adapter storage LoginStorageTest
/test-adapter email
/test-adapter storage TaskStorageTest
Read ProductSpecification/technology.md Conventions table for the backend test command pattern. Adapter name maps to the adapter module path (e.g., adapters/{adapter}).
Parse arguments: first word is adapter name, optional second word is test filter.
Without test filter:
{Backend test command} with module = adapters/{adapter}
With test filter:
{Backend test command} with module = adapters/{adapter}, filtered to *{filter}*
Report the test results from output.
Continue working on a story or task by reading progress.md, executing the next work unit, and updating progress. Use when user wants to resume story/task work or mentions /continue command.
Create a new task (bug, refactoring, or qa) with spec and progress tracking. Use when user wants to create a task or mentions /task command.
Run tests with coverage and report uncovered lines/branches per class. Use when user wants to check test coverage, find untested code, identify coverage gaps, or mentions /test-coverage command. Also use after green phases to verify new code is well-covered.
Review tests to replace loose validation (contains, isNotNull, isNotEmpty) with strict validation (isEqualTo on parsed fields). Use when user wants to improve test assertions or mentions /test-review command.