From testing-plugin
Consults test-architecture agent for testing strategy and design including coverage gaps, flaky tests, framework selection, test pyramid analysis, and new feature test planning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/testing-plugin:test-consultopusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Explicit command to consult the `test-architecture` agent for strategic testing decisions.
Explicit command to consult the test-architecture agent for strategic testing decisions.
Use when:
| Topic | What it covers |
|---|---|
coverage | Analyze gaps, recommend high-value tests to write |
strategy | Review overall test architecture and pyramid |
framework | Recommend testing tools for tech stack |
flaky | Diagnose and remediate flaky tests |
pyramid | Analyze test tier distribution |
new-feature | Design test approach for new functionality |
| (free text) | Custom question about testing |
$1: Topic keyword or natural language question--context <path>: Focus analysis on specific directoryGather Project Context:
Delegate to test-architecture Agent:
Present Recommendations:
# Coverage analysis
/test:consult coverage
# New feature testing strategy
/test:consult new-feature --context src/auth/
# Framework decision
/test:consult "Should we add property-based testing?"
# Flaky test investigation
/test:consult flaky
# Custom question
/test:consult "How should we structure tests for our API endpoints?"
This command delegates to the test-architecture agent with:
The agent will provide:
npx claudepluginhub laurigates/claude-plugins --plugin testing-pluginDesign testing strategies (unit, integration, end-to-end, performance) that catch bugs without creating bottlenecks. Use when scaling testing or improving release confidence.
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
Use when writing tests, designing test strategy, or reviewing test coverage. Covers test pyramid, naming, mocking, and flaky test policy.