running-integration-tests
について
このスキルは、Claudeが統合テストスイートを実行・管理することを可能にし、環境構築、データベースのシーディング、サービスオーケストレーションを自動化します。開発者が統合テストの実行を依頼したり、`/run-integration`のようなトリガーを使用した際にご利用ください。依存サービスの管理、マイグレーション、クリーンアップを含む完全なライフサイクルを処理し、信頼性の高いテスト実行を実現します。
クイックインストール
Claude Code
推奨/plugin add https://github.com/jeremylongshore/claude-code-plugins-plusgit clone https://github.com/jeremylongshore/claude-code-plugins-plus.git ~/.claude/skills/running-integration-testsこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストールします
ドキュメント
Overview
This skill empowers Claude to execute comprehensive integration tests, ensuring seamless interactions between various system components. It automates the often complex setup and teardown processes, providing reliable and repeatable test runs.
How It Works
- Environment Preparation: The plugin sets up the test environment, including creating/resetting databases, running migrations, and seeding test data.
- Test Execution: The plugin executes the integration test suites, capturing detailed logs and reporting progress.
- Cleanup: After the tests, the plugin cleans up the environment, dropping the test database, stopping services, and removing temporary files to prevent test pollution.
When to Use This Skill
This skill activates when you need to:
- Run all integration tests for a project.
- Run a specific integration test suite (e.g., "API tests").
- Run integration tests with code coverage analysis.
Examples
Example 1: Running All Integration Tests
User request: "/run-integration"
The skill will:
- Prepare the test environment (database, services).
- Execute all integration test suites defined in the project.
- Generate a report with pass/fail counts and coverage metrics.
- Clean up the test environment.
Example 2: Running a Specific Test Suite
User request: "/run-integration api"
The skill will:
- Prepare the test environment.
- Execute only the "api" integration test suite.
- Generate a report specific to the "api" suite.
- Clean up the test environment.
Best Practices
- Configuration: Ensure test configurations are properly set up in
test/integration/config.json,.env.test, or related files. - Dependencies: Define all necessary services and dependencies in the test environment configuration.
- Test Design: Write focused integration tests that verify specific interactions between components.
Integration
This skill works seamlessly with other plugins by ensuring a clean and isolated test environment. It avoids conflicts with other processes and provides reliable results.
GitHub リポジトリ
関連スキル
content-collections
メタThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
creating-opencode-plugins
メタThis skill provides the structure and API specifications for creating OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It offers implementation patterns for JavaScript/TypeScript modules that intercept and extend the AI assistant's lifecycle. Use it when you need to build event-driven plugins for monitoring, custom handling, or extending OpenCode's capabilities.
evaluating-llms-harness
テストThis Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.
sglang
メタSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.