testing-plugin/skills/test-consult/SKILL.md
Consult the test-architecture agent for strategy decisions. Use when asking about coverage gaps, test pyramid, framework selection, flaky-test remediation, or how to test X.
npx skillsauth add laurigates/claude-plugins test-consultInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Use this skill when... | Use test-tier-selection instead when... | |---|---| | Asking strategic "how should we test X?" questions | Mechanically picking unit vs integration vs E2E for a change | | Designing the test approach for a new feature | Running the actual tests (use test-run, test-quick, test-full) | | Diagnosing flaky-test root causes | Setting up a fresh project's test infrastructure (use test-setup) | | Reviewing pyramid balance or coverage gaps | Triaging concrete failing-test output (use test-analyze) |
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:
testing
Verify accumulated bug claims at upstream HEAD and dedup against trackers before filing issues. Use when filing upstream reports from backlogs, audit docs, or git-history findings.
documentation
Gate outward-bound text (upstream issues, docs, PR bodies) through isolated haiku fresh-reader critique before publishing. Use when an artifact must survive a reader with zero project context.
tools
Suggest improvements to SKILL.md content, descriptions, or tool config from eval results. Use when raising pass rates, fixing triggering, or iterating on a skill after evaluation.
tools
deadbranch CLI for stale-branch cleanup — dry-run preview, TUI or non-interactive delete, protects main/develop/WIP. Use when asked to clean up branches, prune branches, or remove stale branches.