agent-tester

Generates unit, integration, and e2e tests from code diffs and orchestrator context.

4|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill agent-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-tester
Source: https://github.com/ryan-nguyen-01/agent-platform/tree/main/.claude/Agents/agent-tester
Command: npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill agent-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent writes and runs tests after a coder completes work, receiving a diff and test strategy from the Orchestrator to generate unit, integration, and end-to-end tests that fit the stack.

Core Features & Use Cases

  • Diff-driven test generation: consumes code changes and orchestration context to craft targeted tests for the modified modules.
  • Multi-framework support: supports jest, vitest, pytest, junit, and playwright for unit, integration, and e2e testing.
  • Structured workflow: analyzes scope, defines a test strategy, writes tests, and reports results back to the Orchestrator.

Quick Start

Invoke this skill with the diff and test context from the Orchestrator to generate tests tailored to the target stack.

Frequently Asked Questions about agent-tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate unit and integration tests from a code diff?

You generate unit and integration tests from a code diff by providing the diff data, target stack details, and test framework information. The skill analyzes the modified modules and produces targeted tests with run configurations.

Can I automate test generation for both pytest and jest frameworks?

Yes, you can automate test generation for pytest and jest, as well as vitest, junit, and playwright. The skill supports these frameworks to produce unit, integration, and end-to-end tests.

What do I need to provide to automate e2e testing from code changes?

To automate e2e testing from code changes, you need to provide the code diff, orchestrator context with test strategy, target stack details, and the test framework information. The skill uses these inputs to generate tests.

What's the best way to structure a test strategy after a coder completes work?

The best way to structure a test strategy after coding is to pass the diff and orchestration context to the skill. It analyzes the scope, defines a strategy, writes unit, integration, and e2e tests, and reports results.

Does automated test generation work across multiple project stacks?

Yes, automated test generation works across multiple project stacks. The skill applies the provided stack details and test framework information to generate tests that fit your specific project environment.

Why do I need orchestrator context to generate tests from diffs?

Orchestrator context provides the test strategy and scope analysis needed to generate targeted tests. Without it, the skill cannot determine the structured workflow required to produce unit, integration, and e2e tests from the diff.