> orchestrating-test-workflows
This skill enables Claude to orchestrate complex test workflows using the test-orchestrator plugin. It allows Claude to define test execution graphs with dependencies, execute tests in parallel, and intelligently select tests to run based on code changes. Use this skill when a user requests test orchestration, dependency management for tests, parallel test execution, smart test selection, or CI/CD integration for testing. Trigger terms include "orchestrate tests", "test workflow", "parallel test
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/test-orchestrator?format=md"Overview
This skill empowers Claude to manage and execute complex test suites efficiently. It leverages the test-orchestrator plugin to handle test dependencies, parallel execution, and intelligent test selection, resulting in faster and more reliable testing processes.
How It Works
- Workflow Definition: Claude uses the plugin to define the test workflow, specifying dependencies between tests.
- Parallelization: The plugin identifies independent tests and executes them in parallel to reduce overall execution time.
- Smart Selection: Based on code changes, the plugin selects only the affected tests to run, minimizing unnecessary execution.
When to Use This Skill
This skill activates when you need to:
- Optimize test execution time.
- Manage dependencies between tests.
- Run only relevant tests after code changes.
Examples
Example 1: Optimizing Regression Testing
User request: "Orchestrate the regression tests for the user authentication module after the recent code changes."
The skill will:
- Use the test-orchestrator plugin to identify the tests affected by the changes in the user authentication module.
- Execute those tests in parallel, respecting any dependencies.
Example 2: Setting up a CI/CD Pipeline
User request: "Set up a test workflow for the CI/CD pipeline that runs unit tests, integration tests, and end-to-end tests with appropriate dependencies."
The skill will:
- Define a test workflow using the test-orchestrator plugin, specifying the order and dependencies between the different test suites (unit, integration, end-to-end).
- Configure the pipeline to trigger the orchestrated test execution upon code commits.
Best Practices
- Dependency Mapping: Clearly define dependencies between tests to ensure correct execution order.
- Granularity: Break down large test suites into smaller, more manageable units for better parallelization.
- Change Tracking: Integrate the test-orchestrator with version control to accurately identify affected tests.
Integration
This skill integrates with the test-orchestrator plugin and can be incorporated into CI/CD pipelines. It can also be used in conjunction with other code analysis tools to further refine test selection.
> related_skills --same-repo
> fathom-cost-tuning
Optimize Fathom API usage and plan selection. Trigger with phrases like "fathom cost", "fathom pricing", "fathom plan".
> fathom-core-workflow-b
Sync Fathom meeting data to CRM and build automated follow-up workflows. Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs, or creating automated post-meeting email summaries. Trigger with phrases like "fathom crm sync", "fathom salesforce", "fathom follow-up", "fathom post-meeting workflow".
> fathom-core-workflow-a
Build a meeting analytics pipeline with Fathom transcripts and summaries. Use when extracting insights from meetings, building CRM sync, or creating automated meeting follow-up workflows. Trigger with phrases like "fathom analytics", "fathom meeting pipeline", "fathom transcript analysis", "fathom action items sync".
> fathom-common-errors
Diagnose and fix Fathom API errors including auth failures and missing data. Use when API calls fail, transcripts are empty, or webhooks are not firing. Trigger with phrases like "fathom error", "fathom not working", "fathom api failure", "fix fathom".