team-test_skill

Overview

This skill automatically configures and launches an Agent Team that generates comprehensive tests for a specified code target. It analyzes the target to detect code type, selects appropriate test-writer agents, spawns them in parallel, and synthesizes a consolidated test suite and coverage report. The lead agent coordinates selection, de-duplication, and final verification of test results.

How this skill works

The skill parses the provided target scope (file, directory, PR, commit, diff, or free-text) and runs a code analysis to classify testable surfaces (business logic, API, UI, data layer, utilities, integration points). It applies a selection matrix to decide which specialized test-writer agents to spawn, sends a single parallel Task call that boots the chosen agents with full target context, and then synthesizes their outputs into tests, a coverage report, and maintenance notes.

When to use it

• When you need bulk generation of tests across a repository or a specific module.
• When entering a new codebase and you want an initial comprehensive test suite.
• When preparing a PR or release and you need fast coverage assessment.
• When automating test creation for CI pipelines or QA bootstrapping.
• When you want a coordinated set of unit, integration, edge, and security tests.

Best practices

• Provide a clear scope flag (--pr, --commit, path, or free-text) so scope detection is deterministic.
• Include existing tests and fixtures in the target context to avoid redundant test generation.
• Prefer thoroughness: when analysis is uncertain, include conditional writers to maximize coverage.
• Run the generated test suite in an isolated environment (containers) before merging.
• Review the lead’s untestable-code list and apply suggested refactors to improve future coverage.

Example use cases

• Automatically build tests for a feature branch before merging to catch regressions.
• Generate an initial test suite for a legacy module to enable safe refactoring.
• Add contract and snapshot tests for API responses after a breaking-change PR.
• Create performance and security tests for an endpoint identified as critical.
• Seed CI with mocks and fixtures to speed up downstream integration testing.